| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
As the finishing touch on commit 3860, completely decouple the termbox
API between moving the cursor and printing at the cursor.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
To achieve this we have to switch to a model of the screen in termbox that
is closer to the underlying terminal.
Before:
a screen is a grid of characters
writing out of bounds does nothing
After:
a screen is a scrolling raster of characters
writing out of bounds wraps to next line and scrolls if necessary
To move to the new model, it was essential that I migrate my fake screen
at the same time to mimic it. This is why the first attempt (commit 3824)
failed (commit 3858). This is also why this commit can't be split into
smaller pieces.
The fake screen now 'scrolls' by rotating screen lines from top to bottom.
There's still no notion of a scrollback buffer.
The newer model is richer; it permits repl-like apps that upstream termbox
can't do easily. It also permits us to simply use `printf` or `cout` to
write to the screen, and everything mostly works as you would expect. Exceptions:
a) '\n' won't do what you expect. You need to explicitly print both '\n'
and '\r'.
b) backspace won't do what you expect. It only moves the cursor back,
without erasing the previous character. It does not wrap.
Both behaviors exactly mimic my existing terminal's emulation of vt100.
The catch: it's easy to accidentally scroll in apps. Out-of-bounds prints
didn't matter before, but they're bugs now. To help track them down, use
the `save-top-idx`, `assert-no-scroll` pair of helpers.
An important trick is to wrap the cursor before rather after printing
a character. Otherwise we end up scrolling every time we print to the
bottom-right character. This means that the cursor position can be invalid
at the start of a print, and we need to handle that.
In the process we also lose the ability to hide and show the screen. We
have to show the prints happening. Seems apt for a "white-box" platform
like Mu.
|
| | |
|
| |
|
|
|
|
|
| |
Lose the ability to hide the cursor. If we want to stop buffering the screen
in termbox, it needs to go.
What's more, it has no tests.
|
| | |
|
| |
|
|
|
| |
Bugfix on commit 3853: clear `render-all-on-no-more-events` once you've
actually run the `render-all`.
|
| | |
|
| |
|
|
| |
Revert commits 3824, 3850 and 3852. We'll redo them more carefully.
|
| |
|
|
|
|
| |
Bring back commit 3844, albeit in simplified form. I'd forgotten that the
one place where we still need to buffer rendering is when people hold down
up/down arrow keys.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Bugfix of commit 3850 for the sandbox/ app. I'd hoped to just quickly move
past this ugly approach, but a cleaner way is more involved than I thought.
This way is ugly partly because I'm introducing a bunch of conditionals
without testing them. One or more of my additions may well be hiding bugs.
Or I may need to add them in a few other places.
The clean way is to update the fake screen model to accurately mimic the
new real screen, where out of bounds prints aren't silently ignored, and
where scrolling is a fact of life.
|
| | |
|
| |
|
|
|
| |
Bugfix: writes out of bounds used to be skipped, but started clobbering
the screen on commit 3824.
|
| | |
|
| |
|
|
|
| |
Improve an error message.
Still lots of room for improving how we render reagents in errors.
|
| |
|
|
|
| |
Fix a crash on an invalid program. Thanks Lakshman Swaminathan for reporting
this issue.
|
| |
|
|
| |
Be more robust to stray files with numeric prefixes.
|
| | |
|
| |
|
|
|
| |
Once I start optimizing most events to not repaint everything there's no
need to be smart about queued-up events.
|
| | |
|
| |
|
|
|
|
|
| |
Always start with an untouched screen that can scroll on printing "\r\n".
We can still clear the screen as needed.
Also drop support for hiding the cursor.
|
| |
|
|
|
| |
Use the real original instruction in error messages.
Thanks Ella Couch.
|
| |
|
|
|
|
|
|
| |
Fix CI.
Our previous approach was breaking because a test was generating different
results depending on what layer you stopped at. Turns out we rename instructions
in layer 54. So let's save the original_name in the same layer.
|
| |
|
|
|
|
| |
Fix CI.
In the process I also fixed a bug in the tangle/ utility.
|
| |
|
|
|
|
|
| |
Expanded instructions don't seem to be worth the space they take up. Let
people think through the types of variables for themselves.
Thanks again to Ella Couch.
|
| | |
|
| |
|
|
| |
Fix CI.
|
| | |
|
| | |
|
| |
|
|
| |
Loosen type-checking slightly to accomodate type abbreviations.
|
| |
|
|
|
| |
More fixes for commit 3828 (supporting buffers of something other than
characters).
|
| |
|
|
| |
Fix CI.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Now it's much more apparent why things are slow. You can see each repaint
happening. Already I fixed one performance bug -- in clear-rest-of-screen.
Since this subverts Mu's fake screen there may be bugs.
Another salubrious side effect: I've finally internalized that switching
to raw mode doesn't have to clear the screen. That was just an artifact
of how termbox abstracted operations. Now I can conceive of using termbox
to build a repl as well.
(I was inspired to poke into termbox internals by
http://viewsourcecode.org/snaptoken/kilo and
https://github.com/antirez/linenoise)
|
| | |
|
| |
|
|
|
|
| |
Provide an option to disable memory reclamation. This makes edit/ *much*
more responsive. The cost: memory use grows monotonically. Since we no
longer have a safe way to reclaim heap allocations, we never do so.
|
| |
|
|
| |
Fix CI.
|
| | |
|
| |
|
|
|
|
|
| |
Yet another attempt at trying to clean up commit 3216. I think this solution
might finally let me stop agonizing over the problem. State variables for
distinguishing call-sites are a reasonable mechanism, orthogonal to waypoints
and the hook functions to hold them.
|
| |
|
|
| |
Thanks Ella Couch for suggesting this approach.
|
| |
|
|
| |
Thanks Ella Couch for reporting this issue.
|
| |
|
|
|
|
|
|
| |
Resize events don't actually seem to ever get queued up, so they're still
super slow. Dump all our extra smarts about skipping repaints. We need
to focus on speeding up repaints in general.
Thanks Andrew Owen for reporting this issue.
|
| |
|
|
|
| |
Turns out enabling profiling requires '-pg' to also be passed in to the
linker. Might as well pass all flags everywhere.
|
| |
|
|
|
|
| |
Initial baby steps at trying to understand why rendering to screen is so
slow in Mu. I'd forgotten about this old "poor man's profiler" I'd added
back in 2015.
|
| | |
|