| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | . | Kartik K. Agaram | 2021-06-04 | 1 | -0/+4 |
| | | | | | Menu shortcut for jumping to function definition. | ||||
| * | . | Kartik K. Agaram | 2021-06-04 | 1 | -8/+8 |
| | | |||||
| * | . | Kartik K. Agaram | 2021-06-04 | 1 | -2/+2 |
| | | | | | Keep hotkeys stable when different elements are in focus. | ||||
| * | . | Kartik K. Agaram | 2021-06-04 | 1 | -8/+7 |
| | | |||||
| * | . | Kartik K. Agaram | 2021-06-03 | 1 | -5/+8 |
| | | |||||
| * | . | Kartik K. Agaram | 2021-06-03 | 1 | -13/+11 |
| | | |||||
| * | . | Kartik K. Agaram | 2021-06-03 | 1 | -2/+2 |
| | | |||||
| * | shell: more stable trace when rerunning | Kartik K. Agaram | 2021-06-02 | 1 | -1/+113 |
| | | |||||
| * | . | Kartik K. Agaram | 2021-05-31 | 1 | -28/+28 |
| | | |||||
| * | shell: raise errors when loading code on boot | Kartik K. Agaram | 2021-05-30 | 1 | -3/+16 |
| | | |||||
| * | bugfix: unbound variables were not raising error | Kartik K. Agaram | 2021-05-30 | 1 | -3/+21 |
| | | | | | | Since we switched error trace semantics from a designated label to a designated depth (commit 9831a8cef9 on May 19). | ||||
| * | first test re-running sandbox with a deeper trace | Kartik K. Agaram | 2021-05-30 | 1 | -3/+74 |
| | | |||||
| * | . | Kartik K. Agaram | 2021-05-30 | 1 | -1/+47 |
| | | |||||
| * | first attempt doesn't work | Kartik K. Agaram | 2021-05-30 | 1 | -0/+9 |
| | | | | | | | I was aware of some complications. The various indexes and y coordinates in the trace's cache would be unstable and need to be recomputed. But it's surprising that the trace _completely disappears_. | ||||
| * | start progressively increasing trace depth | Kartik K. Agaram | 2021-05-30 | 1 | -24/+30 |
| | | | | | | | | | | | | The goal: the sandbox initially maintains a shallow trace. As you expand into the trace, the environment reruns the sandbox at greater depth as needed. The challenge: expanding happens within edit-trace, which doesn't have the whole sandbox needed to re-run the sandbox. We'll either need to expand the trace's capabilities to include the whole sandbox, or duplicate some logic to decide when to run the sandbox. | ||||
| * | disable ctrl-s when browsing trace | Kartik K. Agaram | 2021-05-23 | 1 | -2/+6 |
| | | | | | | We're soon going to be dynamically rerunning the sandbox in other ways when browsing the trace. | ||||
| * | . | Kartik K. Agaram | 2021-05-23 | 1 | -4/+4 |
| | | |||||
| * | shell: reduce trace depth in sandbox | Kartik K. Agaram | 2021-05-22 | 1 | -1/+1 |
| | | | | | We'll gradually make this more dynamic. | ||||
| * | disallow null traces | Kartik K. Agaram | 2021-05-19 | 1 | -6/+11 |
| | | | | | | | We now use traces everywhere for error-checking. Null traces introduce the possibility of changing a functions error response, and therefore its semantics. | ||||
| * | shell: traces track a maximum depth to record | Kartik K. Agaram | 2021-05-19 | 1 | -2/+2 |
| | | |||||
| * | shell: add a lot of error-checking | Kartik K. Agaram | 2021-05-18 | 1 | -0/+6 |
| | | |||||
| * | . | Kartik K. Agaram | 2021-05-07 | 1 | -4/+4 |
| | | |||||
| * | an often-overflowing stream when running brcircle | Kartik K. Agaram | 2021-05-07 | 1 | -0/+2 |
| | | | | | We really need to systematically check our trace streams. | ||||
| * | . | Kartik K. Agaram | 2021-05-07 | 1 | -3/+3 |
| | | |||||
| * | starting to implement first macros | Kartik K. Agaram | 2021-05-07 | 1 | -0/+1 |
| | | | | | | | | | | | | | | | | Another commit, another bugfix. Some snippets from my currently exploding todo list: - always investigate lookup errors immediately. Beyond the root cause, they should never happen at the moment, while we aren't reclaiming memory. we should always return a more precise error message. Usually involving null pointer checks. - on abort, print out stack trace - emit mapping of labels to addresses during survey - store a mapping of symbols somewhere in the code image - stop allocating 1KB per token; expand space for tokens as needed | ||||
| * | back to macros; switch macroexpand to operate in place | Kartik K. Agaram | 2021-05-06 | 1 | -4/+2 |
| | | |||||
| * | shell: start implementing macros | Kartik K. Agaram | 2021-05-04 | 1 | -1/+4 |
| | | |||||
| * | . | Kartik K. Agaram | 2021-05-04 | 1 | -6/+6 |
| | | |||||
| * | . | Kartik K. Agaram | 2021-05-01 | 1 | -3/+3 |
| | | | | | Clean up menus. | ||||
| * | cleaner rendering of fake screens and keyboards | Kartik K. Agaram | 2021-05-01 | 1 | -116/+9 |
| | | | | | | | I don't understand why a second line in the keyboard is visible now where it wasn't before. That whole aspect has unclear desires. What exactly do I want to happen on newlines? | ||||
| * | . | Kartik K. Agaram | 2021-05-01 | 1 | -49/+63 |
| | | | | | Use sandbox background in the top line on the right. | ||||
| * | move color scheme closer to Solarized dark | Kartik K. Agaram | 2021-05-01 | 1 | -50/+50 |
| | | | | | | | | | | | | | | sed -i 's,0x12/bg=almost-black,0xdc/bg=green-bg,g' shell/*.mu sed -i 's, 0/bg, 0xc5/bg=blue-bg,g' shell/*.mu sed -i 's, 7/fg=trace, 0x38/fg=trace,g' shell/*.mu sed -i 's, 7/bg=grey, 0x5c/bg=black,g' shell/*.mu Still a few issues. Thanks Adrian Cochrane and Zach DeCook. https://floss.social/@alcinnz/106152068473019933 https://social.librem.one/@zachdecook/106159988837603417 | ||||
| * | shell: squeeze menu | Kartik K. Agaram | 2021-04-30 | 1 | -11/+13 |
| | | |||||
| * | adjust fake screen aspect ratio for verisimilitude | Kartik K. Agaram | 2021-04-29 | 1 | -1/+1 |
| | | |||||
| * | make pixel borders of screen clear | Kartik K. Agaram | 2021-04-29 | 1 | -16/+20 |
| | | |||||
| * | make matching parens pop again | Kartik K. Agaram | 2021-04-29 | 1 | -1/+1 |
| | | |||||
| * | white text everywhere by default | Kartik K. Agaram | 2021-04-29 | 1 | -1/+1 |
| | | |||||
| * | adjust some colors and padding | Kartik K. Agaram | 2021-04-29 | 1 | -52/+54 |
| | | |||||
| * | bugfix: initialize gap buffers before using them | Kartik K. Agaram | 2021-04-28 | 1 | -1/+1 |
| | | | | | | | | I keep running into one hole in Mu's memory-safety since dropping the Linux dependency: null pointers no longer error when dereferenced. Here the problem manifests as aliasing: lots of gap buffers share the same exact data near address 0, because it was never initialized. | ||||
| * | shell: load/store from/to disk with indent | Kartik K. Agaram | 2021-04-28 | 1 | -0/+17 |
| | | | | | | Once I came up with the right approach, this worked on the first try once I got the types and registers to line up! | ||||
| * | . | Kartik K. Agaram | 2021-04-28 | 1 | -3/+1 |
| | | |||||
| * | start stashing and clearing sandbox after definitions | Kartik K. Agaram | 2021-04-28 | 1 | -9/+13 |
| | | |||||
| * | shell: stream literals | Kartik K. Agaram | 2021-04-27 | 1 | -0/+17 |
| | | |||||
| * | . | Kartik K. Agaram | 2021-04-27 | 1 | -17/+17 |
| | | |||||
| * | . | Kartik K. Agaram | 2021-04-27 | 1 | -73/+18 |
| | | |||||
| * | shell: use ctrl-m rather than tab to bounce to trace | Kartik K. Agaram | 2021-04-25 | 1 | -9/+9 |
| | | | | | We'll save tab for inserting graphemes. | ||||
| * | devote 2/3rds of screen to definitions | Kartik K. Agaram | 2021-04-25 | 1 | -1/+1 |
| | | |||||
| * | add some padding to the sandbox | Kartik K. Agaram | 2021-04-25 | 1 | -1/+1 |
| | | |||||
| * | clear old output when new run is in progress | Kartik K. Agaram | 2021-04-21 | 1 | -67/+92 |
| | | | | | I'm currently doing this extremely naively/slowly/uglily. Not a bottleneck. | ||||
| * | . | Kartik K. Agaram | 2021-04-21 | 1 | -13/+13 |
| | | |||||