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.
*	6857	Kartik Agaram	2020-09-25	1	-0/+9
\|
*	6853 - tile: initialize a test function definition	Kartik Agaram	2020-09-24	1	-0/+1
\|
*	6845	Kartik Agaram	2020-09-23	1	-27/+30
\|
*	6821 - highlight words clobbered by the next word	Kartik Agaram	2020-09-20	1	-0/+6
\| \| \| \|	Another suggestion from the Future of Software forum.
*	6816 - tile: inserting new words	Kartik Agaram	2020-09-19	1	-8/+26
\|
*	6814 - tile: backspace deletes char or word	Kartik Agaram	2020-09-19	1	-0/+24
\|
*	6812 - tile: render cursor location	Kartik Agaram	2020-09-19	1	-0/+6
\|
*	6811 - tile: left-cursor movement	Kartik Agaram	2020-09-19	1	-0/+36
\| \| \| \| \|	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	-0/+6
\|
*	6806 - tile: place-holder for bottom of stack	Kartik Agaram	2020-09-19	1	-0/+6
\|
*	6805	Kartik Agaram	2020-09-19	1	-13/+13
\|
*	6804 - tile: render all words	Kartik Agaram	2020-09-19	1	-3/+20
\|
*	6801 - snapshot: RPN structured editor	Kartik Agaram	2020-09-19	1	-0/+95
	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