| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
It's bad enough that metadata comments are restricted to integer literals;
let's at least make them work on _all_ integer literals.
|
|
|
|
| |
Convert comments about magic constants into metadata.
|
|
|
|
| |
https://github.com/akkartik/mu/issues/45#issuecomment-719990879, task 2.
|
| |
|
|
|
|
| |
Strings can contain spaces.
|
| |
|
|
|
|
|
| |
Constructing new functions with ctrl-d is now working right. But the call
seems exactly flipped.
|
| |
|
|
|
|
|
| |
Snapshot: tile currently segfaulting. I need to back up and make it easier
to debug.
|
| |
|
|
|
|
| |
Another suggestion from the Future of Software forum.
|
| |
|
| |
|
|
|
|
|
| |
Displayed cursor position is not yet correct, but insertions happen at
the right cursor position.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
Extremely hacky initial stab at a 1-line editor.
|
|
|