mu - Soul of a tiny new machine. More thorough tests → More comprehensible and rewrite-friendly software → More resilient society.

	Commit message (Collapse)	Author	Age	Files	Lines
*	6822	Kartik Agaram	2020-09-20	1	-2/+2
\|
*	6821 - highlight words clobbered by the next word	Kartik Agaram	2020-09-20	3	-0/+75
\| \| \| \|	Another suggestion from the Future of Software forum.
*	6820	Kartik Agaram	2020-09-20	1	-1/+1
\|
*	6819	Kartik Agaram	2020-09-20	1	-4/+4
\|
*	6818 - color top of stack	Kartik Agaram	2020-09-20	1	-0/+3
\| \| \| \|	Suggestion from the Future of Software group (https://futureofcoding.slack.com/archives/C0120A3L30R/p1600591669008700?thread_ts=1600587602.007800)
*	6817	Kartik Agaram	2020-09-19	1	-1/+7
\|
*	6816 - tile: inserting new words	Kartik Agaram	2020-09-19	1	-8/+26
\|
*	6815 - tile: get actual calculations working	Kartik Agaram	2020-09-19	1	-30/+32
\|
*	6814 - tile: backspace deletes char or word	Kartik Agaram	2020-09-19	3	-0/+58
\|
*	6813 - tile: right-cursor is now easy	Kartik Agaram	2020-09-19	1	-7/+22
\|
*	6812 - tile: render cursor location	Kartik Agaram	2020-09-19	3	-4/+26
\|
*	6811 - tile: left-cursor movement	Kartik Agaram	2020-09-19	3	-5/+68
\| \| \| \| \|	Displayed cursor position is not yet correct, but insertions happen at the right cursor position.
*	6810 - tile: adaptive column widths	Kartik Agaram	2020-09-19	1	-2/+7
\|
*	6807 - tile: render intermediate stack state	Kartik Agaram	2020-09-19	5	-61/+191
\|
*	6806 - tile: place-holder for bottom of stack	Kartik Agaram	2020-09-19	2	-16/+25
\|
*	6805	Kartik Agaram	2020-09-19	1	-13/+13
\|
*	6804 - tile: render all words	Kartik Agaram	2020-09-19	2	-8/+37
\|
*	6803 - RPN: typing a single word now works	Kartik Agaram	2020-09-19	2	-30/+9
\|
*	6801 - snapshot: RPN structured editor	Kartik Agaram	2020-09-19	5	-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
*	6798	Kartik Agaram	2020-09-17	1	-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.
*	6797	Kartik Agaram	2020-09-17	1	-12/+10
\|
*	6796	Kartik Agaram	2020-09-16	3	-52/+194
\| \| \| \|	Extremely hacky initial stab at a 1-line editor.
*	6792	Kartik Agaram	2020-09-16	1	-1/+0
\| \| \| \|	Roll back all buffering of Stdout.
*	6790 experiment: explicit flush	Kartik Agaram	2020-09-16	1	-0/+1
\| \| \| \| \| \| \| \| \|	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 screen	Kartik Agaram	2020-09-16	3	-0/+225
\|
*	6787	Kartik Agaram	2020-09-16	1	-2/+33
\|
*	6776 - new app: a programming environment	Kartik Agaram	2020-09-13	3	-0/+426
	This will take a while.