about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
* 6822Kartik Agaram2020-09-201-2/+2
|
* 6821 - highlight words clobbered by the next wordKartik Agaram2020-09-205-4/+79
| | | | Another suggestion from the Future of Software forum.
* 6820Kartik Agaram2020-09-201-1/+1
|
* 6819Kartik Agaram2020-09-201-4/+4
|
* 6818 - color top of stackKartik Agaram2020-09-201-0/+3
| | | | Suggestion from the Future of Software group (https://futureofcoding.slack.com/archives/C0120A3L30R/p1600591669008700?thread_ts=1600587602.007800)
* 6817Kartik Agaram2020-09-191-1/+7
|
* 6816 - tile: inserting new wordsKartik Agaram2020-09-191-8/+26
|
* 6815 - tile: get actual calculations workingKartik Agaram2020-09-191-30/+32
|
* 6814 - tile: backspace deletes char or wordKartik Agaram2020-09-193-0/+58
|
* 6813 - tile: right-cursor is now easyKartik Agaram2020-09-191-7/+22
|
* 6812 - tile: render cursor locationKartik Agaram2020-09-193-4/+26
|
* 6811 - tile: left-cursor movementKartik Agaram2020-09-193-5/+68
| | | | | Displayed cursor position is not yet correct, but insertions happen at the right cursor position.
* 6810 - tile: adaptive column widthsKartik Agaram2020-09-192-2/+8
|
* 6809Kartik Agaram2020-09-192-1/+118
|
* 6808Kartik Agaram2020-09-192-2/+2
|
* 6807 - tile: render intermediate stack stateKartik Agaram2020-09-198-62/+267
|
* 6806 - tile: place-holder for bottom of stackKartik Agaram2020-09-192-16/+25
|
* 6805Kartik Agaram2020-09-191-13/+13
|
* 6804 - tile: render all wordsKartik Agaram2020-09-192-8/+37
|
* 6803 - RPN: typing a single word now worksKartik Agaram2020-09-192-30/+9
|
* 6802 - plug a gaping hole in the Mu translatorKartik Agaram2020-09-192-0/+125
| | | | | This issue hasn't been noticed until now because I haven't been using variables on the stack much.
* 6801 - snapshot: RPN structured editorKartik Agaram2020-09-195-92/+583
| | | | | | | | | | | | | | | 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
* 6800Kartik Agaram2020-09-191-2/+2
|
* 6799Kartik Agaram2020-09-181-1/+1
|
* 6798Kartik Agaram2020-09-171-43/+7
| | | | | | | Simplify the app for now. I'm not actually sure what sort of language I want to create here. So let's not get ahead of ourselves inventing a whole new grid model and everything.
* 6797Kartik Agaram2020-09-171-12/+10
|
* 6796Kartik Agaram2020-09-164-53/+195
| | | | Extremely hacky initial stab at a 1-line editor.
* 6795Kartik Agaram2020-09-161-0/+0
| | | | Fix CI since commit 6787.
* 6794 - cleaner interface for keyboardKartik Agaram2020-09-1637-53/+61
| | | | | | | So far I've been assuming that read-key only works for ascii, and that I'd need to get more sophisticated both for multi-byte utf-8 and multi-byte terminal escape codes like arrow keys. Rather to my surprise, both work fine. We just need to adjust the types to reflect this fact.
* 6793Kartik Agaram2020-09-168-516/+83
|
* 6792Kartik Agaram2020-09-164-44/+26
| | | | Roll back all buffering of Stdout.
* 6791Kartik Agaram2020-09-162-1/+8
| | | | Yeah, this isn't working.
* 6790 experiment: explicit flushKartik Agaram2020-09-164-26/+37
| | | | | | | | | tile is already visibly slow (49x212 screen) :/ So programmer needs more control over performance. But this may not be the right approach. That extra flush-stdout in tui.mu suggests it's either going to be finicky, or we have to flush on every attribute change. And going through a buffered-file may be slower. May.
* 6789 - tile: print keystrokes to screenKartik Agaram2020-09-163-0/+225
|
* 6788Kartik Agaram2020-09-162-0/+13
|
* 6787Kartik Agaram2020-09-161-2/+33
|
* 6786Kartik Agaram2020-09-161-5/+5
|
* 6785Kartik Agaram2020-09-162-2/+2
|
* 6784Kartik Agaram2020-09-161-2/+2
|
* 6783Kartik Agaram2020-09-1614-0/+49
| | | | An extra test that should have been in commit 6781.
* 6782Kartik Agaram2020-09-152-0/+15
| | | | | | | Regression: segfault on `fn foo` without a block I really need to turn the list of scenarios considered before populate-mu-function-header into tests.
* 6781 - new app: RPN (postfix) calculatorKartik Agaram2020-09-1523-12/+451
| | | | This was surprisingly hard; bugs discovered all over the place.
* 6780Kartik Agaram2020-09-141-0/+0
|
* 6779Kartik Agaram2020-09-142-1/+1
| | | | Looks like Linux turns reads from stdout/stderr into stdin!
* 6778Kartik Agaram2020-09-143-4/+4
|
* 6777Kartik Agaram2020-09-145-9/+56
| | | | Print answers in decimal in apps/arith.mu
* 6776 - new app: a programming environmentKartik Agaram2020-09-133-0/+426
| | | | This will take a while.
* 6775Kartik Agaram2020-09-111-0/+11
|
* 6774Kartik Agaram2020-09-1126-1228/+2627
|
* 6773 - markdown browser now seems fully testedKartik Agaram2020-09-111-0/+56
|