Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | . | Kartik K. Agaram | 2021-06-04 | 2 | -3/+3 |
| | |||||
* | . | Kartik K. Agaram | 2021-06-04 | 1 | -4/+4 |
| | |||||
* | . | Kartik K. Agaram | 2021-06-04 | 1 | -0/+54 |
| | | | | Keyboard state machine for jumping to function definition. | ||||
* | . | Kartik K. Agaram | 2021-06-04 | 2 | -0/+6 |
| | | | | Menu shortcut for jumping to function definition. | ||||
* | . | Kartik K. Agaram | 2021-06-04 | 2 | -11/+11 |
| | |||||
* | . | Kartik K. Agaram | 2021-06-04 | 2 | -5/+5 |
| | | | | Keep hotkeys stable when different elements are in focus. | ||||
* | . | Kartik K. Agaram | 2021-06-04 | 4 | -10/+10 |
| | |||||
* | . | Kartik K. Agaram | 2021-06-04 | 1 | -2/+2 |
| | |||||
* | . | Kartik K. Agaram | 2021-06-04 | 1 | -3/+3 |
| | |||||
* | . | Kartik K. Agaram | 2021-06-04 | 1 | -2/+2 |
| | |||||
* | . | Kartik K. Agaram | 2021-06-04 | 1 | -2/+0 |
| | |||||
* | . | Kartik K. Agaram | 2021-06-04 | 1 | -5/+5 |
| | |||||
* | . | Kartik K. Agaram | 2021-06-04 | 1 | -2/+2 |
| | |||||
* | . | Kartik K. Agaram | 2021-06-04 | 1 | -1/+1 |
| | |||||
* | more convenient 'def' | Kartik K. Agaram | 2021-06-04 | 1 | -30/+32 |
| | |||||
* | rename the definition primitive to 'def' | Kartik K. Agaram | 2021-06-04 | 4 | -40/+40 |
| | |||||
* | . | Kartik K. Agaram | 2021-06-03 | 3 | -7/+22 |
| | |||||
* | starting to support function editing | Kartik K. Agaram | 2021-06-03 | 2 | -1/+13 |
| | |||||
* | . | Kartik K. Agaram | 2021-06-03 | 2 | -1597/+1601 |
| | |||||
* | . | Kartik K. Agaram | 2021-06-03 | 2 | -156/+184 |
| | |||||
* | . | Kartik K. Agaram | 2021-06-03 | 1 | -5/+5 |
| | |||||
* | . | Kartik K. Agaram | 2021-06-03 | 2 | -17/+14 |
| | |||||
* | . | Kartik K. Agaram | 2021-06-03 | 1 | -2/+2 |
| | |||||
* | . | Kartik K. Agaram | 2021-06-03 | 1 | -2/+15 |
| | | | | Drop some low-entropy trace lines. | ||||
* | shell: more stable trace when rerunning | Kartik K. Agaram | 2021-06-02 | 3 | -3/+252 |
| | |||||
* | . | Kartik K. Agaram | 2021-06-02 | 1 | -2/+2 |
| | |||||
* | . | Kartik Agaram | 2021-05-31 | 1 | -17/+19 |
| | | | | State as of https://archive.org/details/akkartik-mu-2021-05-31 | ||||
* | . | Kartik Agaram | 2021-05-31 | 1 | -3/+5 |
| | | | | | Until we get scrolling on functions, it's a little cleaner to draw the primitives on top. | ||||
* | interrupt repl on keypress | Kartik K. Agaram | 2021-05-31 | 1 | -1/+7 |
| | |||||
* | . | Kartik K. Agaram | 2021-05-31 | 1 | -8/+8 |
| | |||||
* | . | Kartik K. Agaram | 2021-05-31 | 4 | -34/+36 |
| | |||||
* | . | Kartik Agaram | 2021-05-31 | 45 | -8126/+9504 |
| | |||||
* | clean up trace depth in a few places | Kartik K. Agaram | 2021-05-31 | 1 | -0/+3 |
| | | | | | It turns out the problem was that `and` wasn't cleaning up after itself when it short-circuited evaluation. Similar problems in a couple more places. | ||||
* | . | Kartik K. Agaram | 2021-05-31 | 1 | -0/+2 |
| | |||||
* | bugfix for disappearing trace | Kartik K. Agaram | 2021-05-31 | 1 | -0/+2 |
| | | | | | | | | It turns out I have a problem with trace depth somewhere which I just wasn't noticing before. Running certain sandboxes (line; maybe loops?) twice was causing traces to no longer start at depth 1, which implies that they weren't terminating at depth 1. This became a lot more obvious since I instituted a max-depth. | ||||
* | . | Kartik K. Agaram | 2021-05-31 | 1 | -3/+3 |
| | |||||
* | data.limg now loading properly again | Kartik K. Agaram | 2021-05-31 | 2 | -2/+8 |
| | |||||
* | clearer test | Kartik K. Agaram | 2021-05-31 | 1 | -34/+3 |
| | | | | | It actually has nothing to do with macros. I just wasn't supporting backquotes outside macros before. | ||||
* | multi-macroexpanding backquote != nested backquote | Kartik K. Agaram | 2021-05-31 | 1 | -1/+129 |
| | | | | | | | | | | | | | | | | | | | | | This was quite difficult to diagnose. The issue I noticed was that brline had stopped working. All the bugs in previous commits were hiding the cause. Once I cleaned them up, I realized the problem was that the `(,x0 ,y0) was triggering the nested-backquote check. The fix was fairly straightforward then (even though I didn't yet understand why). But how to write a test for this? I spent some time trying to do so without defining a macro using literal macros, before I realized: You can't call literal macros; we don't have first-class macros. Trying to insert literal macro support just breaks everything because we have no way to distinguish between a literal macro call and the stage in macroexpand where a symbol has been replaced with its macro definition. How do you explain stuff like this? I grow weary of Lisp. There's still some issue in loading the entire definition of brline from data.limg. | ||||
* | clean up a few things in macro tests | Kartik K. Agaram | 2021-05-31 | 1 | -57/+46 |
| | |||||
* | . | Kartik K. Agaram | 2021-05-30 | 1 | -0/+75 |
| | |||||
* | shell: raise errors when loading code on boot | Kartik K. Agaram | 2021-05-30 | 2 | -16/+29 |
| | |||||
* | bugfix: unbound variables were not raising error | Kartik K. Agaram | 2021-05-30 | 6 | -8/+40 |
| | | | | | Since we switched error trace semantics from a designated label to a designated depth (commit 9831a8cef9 on May 19). | ||||
* | . | Kartik K. Agaram | 2021-05-30 | 1 | -3/+3 |
| | |||||
* | unconditionally trace errors | Kartik K. Agaram | 2021-05-30 | 1 | -60/+0 |
| | | | | | | Now that we never have a null trace, tracing errors is always safe. And now that we're running with low trace max-depth we're more likely to run into problems with missing errors in the trace. | ||||
* | . | Kartik K. Agaram | 2021-05-30 | 1 | -0/+5 |
| | |||||
* | . | Kartik K. Agaram | 2021-05-30 | 1 | -1/+1 |
| | |||||
* | first test re-running sandbox with a deeper trace | Kartik K. Agaram | 2021-05-30 | 2 | -3/+75 |
| | |||||
* | . | Kartik K. Agaram | 2021-05-30 | 1 | -10/+10 |
| | |||||
* | . | Kartik K. Agaram | 2021-05-30 | 1 | -1/+47 |
| |