| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
If I try to run a single test and it triggers an error the trace gets
saved in the current directory, as if I was trying to log an interactive
run. Then when I try to rerun the test the trace tries to load as mu
code, and hilarity ensues. Just log interactive runs in .traces/ as well.
|
| |
|
|
|
| |
Forgot to fix chessboard tests during commit 2022: running sandboxes in
separate routines.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Back on a nice cadence of optimizing one case at a time.
|
| |
|
|
|
|
|
|
|
| |
Redo some of the work of commits 2025-2032. We still need to create
special-cases for each branch, but we'll now always update cursor in a
single place. We'll also have handle-keyboard-event tell its caller
whether it already took care of rendering or not. That way the caller
only falls back to painting the entire screen when necessary. No more
double-painting.
|
| | |
|
| |
|
|
| |
Don't render entire screen when appending to line.
|
| |
|
|
|
| |
Traces were changing based on whether I was loading a .mu file with
'main' or not.
|
| |
|
|
|
|
| |
Mouse clicks towards the right of very wide windows weren't working.
Turns out to be a limitation of the X10 protocol:
https://github.com/nsf/termbox-go/issues/32
|
| | |
|
| |
|
|
| |
Back to checking render performance everywhere.
|
| | |
|
| | |
|
| |
|
|
|
| |
All scenarios should use just numeric locations, and 'run' should
encapsulate the code under test.
|
| |
|
|
|
| |
Standardize on whether screen operations will explicitly write to
'screen' inside scenarios. (Answer: not for setup code, at least.)
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Get all tests passing again. Actually slower now than before, thanks to
double-render when editing the sandbox side. But that is temporary.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
First step: drop the existing optimization of not redrawing after every
character. Gives the editor a jumpy feel. I'm also hoisting the render
into handle-keyboard event as a first step to duplicating it everywhere.
One test temporarily failing: we're gonna sometimes forget to draw the
line below editors.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This time I'm getting rid of all the intricate SCREEN hacking. Now
run-interactive is idiomatic: it creates a recipe on the fly, runs it,
and returns various results and stats about it.
One big consequence of the recipe now running interactively inside a
local-scope: you can't just use numeric addresses anymore -- not without
using /raw. Fixed one of the tests to reflect this.
I realize now that I don't really want my students to be using raw
addresses in their sandboxes, even if that was my idiom for lower-level
scenarios.
Hopefully running sandboxes in separate (synchronous) routines will be
easy now.
|
| |
|
|
|
| |
Still trying to minimize the work around run-interactive so I can build
it with a sandboxed routine rather than a call in editor space.
|
| | |
|
| | |
|
| |
|
|
|
| |
I'm starting to optimize screen-drawing. If I get it wrong, this will be
a work-around.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
I think this can never trigger because 'cursor-column' can't be greater
than 'right'.
|
| | |
|
| | |
|