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
*	6860	Kartik Agaram	2020-09-26	1	-0/+7
\| \| \| \| \|	Snapshot: tile currently segfaulting. I need to back up and make it easier to debug.
*	6837	Kartik Agaram	2020-09-22	1	-160/+0
\|
*	6821 - highlight words clobbered by the next word	Kartik Agaram	2020-09-20	1	-0/+34
\| \| \| \|	Another suggestion from the Future of Software forum.
*	6814 - tile: backspace deletes char or word	Kartik Agaram	2020-09-19	1	-0/+6
\|
*	6812 - tile: render cursor location	Kartik Agaram	2020-09-19	1	-1/+7
\|
*	6811 - tile: left-cursor movement	Kartik Agaram	2020-09-19	1	-0/+12
\| \| \| \| \|	Displayed cursor position is not yet correct, but insertions happen at the right cursor position.
*	6807 - tile: render intermediate stack state	Kartik Agaram	2020-09-19	1	-4/+50
\|
*	6801 - snapshot: RPN structured editor	Kartik Agaram	2020-09-19	1	-37/+219
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	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
*	6796	Kartik Agaram	2020-09-16	1	-14/+34
\| \| \| \|	Extremely hacky initial stab at a 1-line editor.
*	6789 - tile: print keystrokes to screen	Kartik Agaram	2020-09-16	1	-0/+137