about summary refs log tree commit diff stats
path: root/shell/sandbox.mu
Commit message (Collapse)AuthorAgeFilesLines
* .Kartik K. Agaram2021-06-031-13/+11
|
* .Kartik K. Agaram2021-06-031-2/+2
|
* shell: more stable trace when rerunningKartik K. Agaram2021-06-021-1/+113
|
* .Kartik K. Agaram2021-05-311-28/+28
|
* shell: raise errors when loading code on bootKartik K. Agaram2021-05-301-3/+16
|
* bugfix: unbound variables were not raising errorKartik K. Agaram2021-05-301-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 traceKartik K. Agaram2021-05-301-3/+74
|
* .Kartik K. Agaram2021-05-301-1/+47
|
* first attempt doesn't workKartik K. Agaram2021-05-301-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 depthKartik K. Agaram2021-05-301-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 traceKartik K. Agaram2021-05-231-2/+6
| | | | | We're soon going to be dynamically rerunning the sandbox in other ways when browsing the trace.
* .Kartik K. Agaram2021-05-231-4/+4
|
* shell: reduce trace depth in sandboxKartik K. Agaram2021-05-221-1/+1
| | | | We'll gradually make this more dynamic.
* disallow null tracesKartik K. Agaram2021-05-191-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 recordKartik K. Agaram2021-05-191-2/+2
|
* shell: add a lot of error-checkingKartik K. Agaram2021-05-181-0/+6
|
* .Kartik K. Agaram2021-05-071-4/+4
|
* an often-overflowing stream when running brcircleKartik K. Agaram2021-05-071-0/+2
| | | | We really need to systematically check our trace streams.
* .Kartik K. Agaram2021-05-071-3/+3
|
* starting to implement first macrosKartik K. Agaram2021-05-071-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 placeKartik K. Agaram2021-05-061-4/+2
|
* shell: start implementing macrosKartik K. Agaram2021-05-041-1/+4
|
* .Kartik K. Agaram2021-05-041-6/+6
|
* .Kartik K. Agaram2021-05-011-3/+3
| | | | Clean up menus.
* cleaner rendering of fake screens and keyboardsKartik K. Agaram2021-05-011-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. Agaram2021-05-011-49/+63
| | | | Use sandbox background in the top line on the right.
* move color scheme closer to Solarized darkKartik K. Agaram2021-05-011-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 menuKartik K. Agaram2021-04-301-11/+13
|
* adjust fake screen aspect ratio for verisimilitudeKartik K. Agaram2021-04-291-1/+1
|
* make pixel borders of screen clearKartik K. Agaram2021-04-291-16/+20
|
* make matching parens pop againKartik K. Agaram2021-04-291-1/+1
|
* white text everywhere by defaultKartik K. Agaram2021-04-291-1/+1
|
* adjust some colors and paddingKartik K. Agaram2021-04-291-52/+54
|
* bugfix: initialize gap buffers before using themKartik K. Agaram2021-04-281-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 indentKartik K. Agaram2021-04-281-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. Agaram2021-04-281-3/+1
|
* start stashing and clearing sandbox after definitionsKartik K. Agaram2021-04-281-9/+13
|
* shell: stream literalsKartik K. Agaram2021-04-271-0/+17
|
* .Kartik K. Agaram2021-04-271-17/+17
|
* .Kartik K. Agaram2021-04-271-73/+18
|
* shell: use ctrl-m rather than tab to bounce to traceKartik K. Agaram2021-04-251-9/+9
| | | | We'll save tab for inserting graphemes.
* devote 2/3rds of screen to definitionsKartik K. Agaram2021-04-251-1/+1
|
* add some padding to the sandboxKartik K. Agaram2021-04-251-1/+1
|
* clear old output when new run is in progressKartik K. Agaram2021-04-211-67/+92
| | | | I'm currently doing this extremely naively/slowly/uglily. Not a bottleneck.
* .Kartik K. Agaram2021-04-211-13/+13
|
* .Kartik K. Agaram2021-04-211-1/+1
|
* .Kartik K. Agaram2021-04-211-66/+66
|
* shell: show screen state during evaluationKartik K. Agaram2021-04-211-1/+1
| | | | | | | | | | | | | | All highly experimental. Current constraints: * No tail recursion elimination * No heap reuse * Keep implementation simple So it's slow, and I don't want to complicate it to speed it up. So I'm investing in affordances to help deal with the slowness. However, in the process I've taken the clean abstraction of a trace ("all you need to do is add to the trace") and bolted on call counts and debug-prints as independent mechanisms.
* an interface approximating stack tracesKartik K. Agaram2021-04-201-3/+3
|
* get bresenham line drawing working with a traceKartik K. Agaram2021-04-201-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | (brline . (fn () (screen x0 y0 x1 y1 color) ((fn (dx dy sx sy) ((fn (err) (brline1 screen x0 y0 x1 y1 dx dy sx sy err color)) (+ dx dy))) (abs (- x1 x0)) (- 0 (abs (- y1 y0))) (sgn (- x1 x0)) (sgn (- y1 y0))))) (brline1 . (fn () (screen x y xmax ymax dx dy sx sy err color) (pixel screen x y color) (if (andf (= x xmax) (= y ymax)) () ((fn (e2) (brline1 screen (if (>= e2 dy) (+ x sx) x) (if (<= e2 dx) (+ y sy) y) xmax ymax dx dy sx sy (+ err (+ (if (>= e2 dy) dy 0) (if (<= e2 dx) dx 0))) color)) (* err 2))))) sandbox: (brline screen 1 1 5 5 12) There are two ideas stemming from this commit: - I need an extremely compact on-screen trace to underlie the trace UX - perhaps we should start truncating trace lines
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-12-22 09:18:32 +0000