about summary refs log tree commit diff stats
path: root/baremetal
Commit message (Collapse)AuthorAgeFilesLines
* 7804Kartik K. Agaram2021-02-251-0/+124
|
* 7803Kartik K. Agaram2021-02-251-119/+118
|
* 7802Kartik K. Agaram2021-02-243-24/+235
| | | | Better tracing of the tokenization phase.
* 7801 - baremetal/shell: expanding traceKartik K. Agaram2021-02-243-28/+545
|
* 7800Kartik K. Agaram2021-02-241-88/+101
|
* 7799Kartik K. Agaram2021-02-241-9/+9
|
* 7798Kartik K. Agaram2021-02-241-12/+12
|
* 7797Kartik K. Agaram2021-02-231-48/+17
|
* 7796Kartik K. Agaram2021-02-231-3/+4
|
* 7795Kartik K. Agaram2021-02-231-1/+1
|
* 7794Kartik K. Agaram2021-02-232-17/+17
|
* 7793 - baremetal/shell: menuKartik K. Agaram2021-02-224-51/+96
|
* 7792Kartik K. Agaram2021-02-221-0/+53
|
* 7791Kartik K. Agaram2021-02-222-50/+37
| | | | Reorganize keyboard handling.
* 7790Kartik K. Agaram2021-02-222-5/+140
|
* 7789Kartik K. Agaram2021-02-224-35/+58
| | | | Start adding some lines to the trace. Never shown yet.
* 7788Kartik K. Agaram2021-02-223-0/+30
|
* 7787 - baremetal/shell: moving cursor into traceKartik K. Agaram2021-02-224-12/+141
|
* 7786 - baremetal/shell: render error messagesKartik K. Agaram2021-02-223-13/+172
|
* 7785 - baremetal/shell: trace primitives doneKartik K. Agaram2021-02-223-5/+86
| | | | Rendering traces will be an ongoing journey.
* 7784 - baremetal/shell: start of traceKartik K. Agaram2021-02-223-11/+56
|
* 7783 - baremetal: no, delete trace streamKartik K. Agaram2021-02-223-868/+84
| | | | | What we need in baremetal is subtly different. We need depths in each line. Just rebuild it from scratch.
* 7782 - baremetal: provide a trace streamKartik K. Agaram2021-02-223-84/+868
|
* 7781 - baremetal/shell: tokenize numbersKartik K. Agaram2021-02-211-0/+93
| | | | | | | | We've now reached a point where we need to start thinking of error handling, and tests for error handling. The top-level has `stop`, but that's really just for working with Unix's exit(). Here we have the opportunity to bake errors into the trace. Which might also be a good opportunity for fleshing out the UX for the trace.
* 7780Kartik K. Agaram2021-02-212-0/+53
| | | | | | Start trimming whitespace from the input. It's probably a bad idea to rebuild all our primitives for gap buffers.
* 7779Kartik K. Agaram2021-02-212-157/+25
|
* 7778Kartik K. Agaram2021-02-211-2/+5
|
* 7777Kartik K. Agaram2021-02-214-16/+69
| | | | Same identity REPL, but now going through some symbol processing.
* 7776Kartik K. Agaram2021-02-211-1/+11
|
* 7775Kartik K. Agaram2021-02-212-18/+18
|
* 7774Kartik K. Agaram2021-02-212-8/+7
| | | | YAGNI over premature optimization. Avoid unnecessary copies.
* 7773Kartik K. Agaram2021-02-212-10/+4
|
* 7772Kartik K. Agaram2021-02-213-20/+29
|
* 7771Kartik K. Agaram2021-02-214-3/+42
| | | | | We might not scan directly through the gap buffer after all. Premature optimization?
* 7770 - baremetal/shell: scanning through gap bufferKartik K. Agaram2021-02-212-1/+168
|
* 7769Kartik K. Agaram2021-02-212-2/+0
|
* 7768 - baremetal/shell: assume multi-line from the startKartik K. Agaram2021-02-211-5/+8
|
* 7767 - baremetal/shell: skeleton replKartik K. Agaram2021-02-214-4/+186
| | | | Prints a fixed value for now, regardless of what is typed.
* 7766Kartik K. Agaram2021-02-211-115/+4
|
* 7765 - baremetal: ctrl keysKartik K. Agaram2021-02-211-32/+80
|
* 7764Kartik K. Agaram2021-02-211-4/+4
|
* 7763 - baremetal/shell: newlineKartik K. Agaram2021-02-203-73/+112
|
* 7762 - baremetal/shell: backspaceKartik K. Agaram2021-02-202-5/+21
| | | | | | The text buffer can now shrink, which means we need to be careful to erase the old location of the cursor. Just clear screen before render each time. Which means we need to be more efficient with our rendering.
* 7761 - baremetal/shell: read input from keyboardKartik K. Agaram2021-02-203-8/+72
|
* 7759 - changing course; delete the postfix shellKartik K. Agaram2021-02-205-3358/+0
| | | | | | | | | | | | | | | | | | | | | | | | It might be too ambitious for an initial Mu system, and I also want to watch my novelty budget. I also have great doubts about the ability of this live-updating postfix system to scale to interesting programs. Conditionals, loops, multi-line functions, all this requires further work. Instead, I'm going to recenter around Mu's original goals: - saying no to most features - encouraging/teaching testing - traces as a unifying metaphor In particular, instead of a live-updating system, the new debug loop will be: - generate a trace - browse the trace - modify the program - generate a trace - ... The only persistence we'll need here is a way to track what the programmer has drilled into in the trace. That might have some commonalities with the old system of expanded words.
* 7758Kartik K. Agaram2021-02-202-0/+1090
| | | | Just some temporary files before I blow them away.
* 7757Kartik K. Agaram2021-02-192-15/+119
|
* 7753Kartik K. Agaram2021-02-151-2/+5
|
* 7752Kartik K. Agaram2021-02-151-2/+20
|
* 7751Kartik K. Agaram2021-02-151-8/+10
|
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-11-20 02:23:45 +0000