| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
| |
Left arrow key out of an expanded word now working.
Still to fix: left arrow key out of the first word in the first word.
|
|
|
|
|
|
|
| |
I just needed to remove an obsolete guardrail in render-line.
Still seeing some bugs with left-arrow when playing around with the full
expansion of `1 2+`.
|
| |
|
|
|
|
|
|
|
| |
Starting to work. I'm still seeing problems in lines with multiple expanded
calls, but perhaps that's a rendering issue.
The code is absolutely ghastly.
|
|
|
|
| |
Cursor now stays on the right row as we bounce in and out of function calls.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Rendering is still ugly. Cursor isn't on the right row. But the hard part
is behind us.
This was a stupid mistake in function-body, and it happened because I've
been getting lazy and passing (addr handle) objects when I should be passing
in "constant" addr objects.
I'm not sure why I was so resistant to debugging by print here. I spent
3 days waffling about with this bug.
|
|
|
|
| |
Tile: simplify the contract for render-column.
|
|
|
|
| |
Changing tack..
|
|
|
|
|
| |
Snapshot. We've gotten arrow keys navigating, but segfault when getting
to the second word in an expanded function call body.
|
| |
|
| |
|
| |
|
|
|
|
| |
Rather surprisingly, this transformation worked the first time!
|
|
|
|
|
|
|
|
|
|
|
|
| |
Snapshot that requires a check in the Mu compiler.
Currently I don't spill a register if it could possibly be over-written
by a function output within. However, find-in-call-path is a good example
of where this constraint is too lenient and results in unsafe code. The
variable `curr` gets clobbered during loop update by the variable `match?`.
What's the answer? Perhaps we should ban all conditional updates to function
outputs? That'd be dashed inconvenient.
|
|
|
|
|
| |
Function expand/contract still works, but the implementation is totally
different under the hood.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Slowly hoist cursor-word from environment to sandbox. This isn't its final
destination.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
We need the state of the stack at the call-site. But rendering is already
working surprisingly well.
|
| |
|
|
|
|
| |
Track just whether to step inside or not.
|
|
|
|
| |
Back to commit 6872.
|
|
|
|
|
| |
Snapshot. Caching subsidiary stacks is a dead end; they're just the final
iteration. We need to render all iterations.
|
| |
|
|
|
|
| |
Hackily show function definition.
|
|
|
|
|
|
| |
Emit a stack of not ints but more complex objects containing the int payload.
Function calls again segfaulting.
|
| |
|
|
|
|
|
| |
Snapshot: tile currently segfaulting. I need to back up and make it easier
to debug.
|
| |
|
|
|
|
|
| |
Get rid of cutesy justify thresholds. They didn't actually save me any
trouble, and they won't generalize to other literals besides ints.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
I actually deleted a test here! Hard-core prototype mode.
|
|
|
|
| |
Initial sketch for a menu bar.
|
|
|
|
| |
Extract "unmoving background" into a separate function.
|
|
|
|
| |
Not sure what I was seeing. clear-screen is plenty stable.
|
|
|
|
|
|
| |
Interestingly, erasing the screen partially looks better to me even though
it's clearly slower. The divider never being redrawn provides a sense of
stability.
|