| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
| |
snapshot: migrating call-path to store word handles rather than word indexes.
ctrl-a and ctrl-e are segfaulting. There are likely other problems.
The major new change here is that allocating a call-path-element no longer
initializes it.
|
| |
|
|
|
|
|
| |
Until now the word being typed had a slightly larger invisible margin,
which was a little strange. Should look cleaner now.
|
| |
|
|
|
|
|
| |
We don't have the static checks for this yet, but discovering I've not
been following my own rules bumps the priority on it.
|
|
|
|
|
| |
I just got bitten by variable shadowing! It's a lot less theoretical concern
now.
|
|
|
|
| |
7013 had broken right-justification when rendering the stack. Redo.
|
| |
|
|
|
|
| |
Fix CI.
|
| |
|
|
|
|
| |
A new example that better demonstrates the value of named arguments.
|
| |
|
| |
|
|
|
|
|
|
| |
Alternative symbols considered for the menu option:
∅
AC (like in a calculator)
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
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+`.
|
|
|
|
|
| |
Bring back definitions for 1+ and 2+. Expanding nested calls still doesn't
work.
|
| |
|
|
|
|
|
| |
Oh, of course. I can't compare the word with the word at the cursor. Not
even its interned pointer. We have to track the call path.
|
|
|
|
|
|
|
| |
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..
|
|
|
|
|
| |
Use the fake-screen infrastructure we already have for non-interactive
mode.
|
|
|
|
|
|
| |
We don't have tests yet in the tile prototype, mostly because we don't
yet feel confident about what desired behavior should be. But it's still
helpful to have a non-interactive mode for tracking down segfaults.
|
|
|
|
|
| |
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!
|