| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
Amazing how easy this was. And it does feel more intuitive. If I decide
at some point that I want to bind something to a name I don't usually want
to lose the entire line after that point.
It also sidesteps for now the thorny question of whether to permit organically
switching to a new line (rather than using the 'name value' hotkey), and
how that should work.
|
| |
|
| |
|
|
|
|
| |
Requires a quick hacky change to Mu compiler.
|
|
|
|
|
| |
Stack display is messed up when file contents contain newlines. Ignoring
that for now.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Some more helpers that I want to avoid using, but they help me gain confidence
in the current implementation of file handles. Manual test:
"x" open dup read swap read
Assumes there's a file called `x` in the current directory that contains
at least two (short!) lines.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
This found several bugs due to me not checking for null strings.
|
| |
|
|
|
|
|
| |
Lesson learned: functions store args in _reverse_ order. Since evaluation
is very frequent, it's worth optimizing for it.
|
|
|
|
|
| |
Snapshot; things seem to be working besides ctrl-r, but we aren't yet rendering
only the final line.
|
|
|
|
| |
We can now create new bindings for names while evaluating lines.
|
| |
|
|
|
|
| |
Extract a new function.
|
|
|
|
| |
Back to commit 6872.
|
|
|
|
| |
Now saving the subsidiary stack.
|
|
|
|
| |
Segfault now fixed. Everything seems to be working again.
|
|
|
|
|
|
| |
Emit a stack of not ints but more complex objects containing the int payload.
Function calls again segfaulting.
|
|
|
|
| |
First function call working in apps/tile!
|
|
|
|
| |
Segfault fixed. This shouldn't have been so hard.
|
|
|
|
|
| |
Snapshot: tile currently segfaulting. I need to back up and make it easier
to debug.
|
| |
|
| |
|
|
|
|
| |
I actually deleted a test here! Hard-core prototype mode.
|
| |
|
| |
|
| |
|
|
There's some worrisome memory corruption here between the call to max-stack-depth
and the callee picking up its args.
All this code is incredibly ugly as I start to wrestle with the challenges
of structured editors. I keep wanting to keep business logic separate from
rendering, but there are feedback loops from wanting to know where to render
the cursor. And I haven't even started trying to avoid full-screen renders
yet. That'll complect things even more. For now the data path for every
iteration of the render loop is:
process key
compute max depth needed (or any other global information needed for rendering)
render
|