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
*	4570	Kartik Agaram	2018-09-21	1	-4/+16
\|
*	4568	Kartik Agaram	2018-09-21	1	-1/+5
\| \| \| \|	Get the 'edit' script working again with the 'EE' command in Vim.
*	4474	Kartik Agaram	2018-08-04	1	-8/+1
\|
*	4323	Kartik Agaram	2018-07-07	1	-0/+13
\|
*	4299	Kartik Agaram	2018-06-30	1	-2/+1
\|
*	4262 - literal 'null'	Kartik Agaram	2018-06-17	1	-1/+2
\|
*	4261 - start using literals for 'true' and 'false'	Kartik Agaram	2018-06-17	1	-0/+1
\| \| \| \| \| \| \| \| \|	They uncovered one bug: in edit/003-shortcuts.mu <scroll-down> was returning 0 for an address in one place where I thought it was returning 0 for a boolean. Now we've eliminated this bad interaction between tangling and punning literals.
*	3976	Kartik K. Agaram	2017-08-20	1	-1/+0
\|
*	3707	Kartik K. Agaram	2016-12-12	1	-1/+3
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	Be more disciplined about tagging 2 different concepts in the codebase: a) Use the phrase "later layers" to highlight places where a layer doesn't have the simplest possible self-contained implementation. b) Use the word "hook" to point out functions that exist purely to provide waypoints for extension by future layers. Since both these only make sense in the pre-tangled representation of the codebase, using '//:' and '#:' comments to get them stripped out of tangled output. (Though '#:' comments still make it to tangled output at the moment. Let's see if we use it enough to be worth supporting. Scenarios are pretty unreadable in tangled output anyway.)
*	3566	Kartik K. Agaram	2016-10-23	1	-3/+4
\| \| \| \| \| \| \| \| \| \| \| \|	vim: Stop loading C++-specific syntax highlighting in non-C++ files. I also figured out why the autocommand wasn't running on the first file: my local setup for directory-specific vimrc files runs inside an autocommand, and it runs autocommands recursively inside an autocommand, and it runs only autocommands inside a 'LocalVimrc' autocommand group to ensure infinite regress (autocommands running multiple times in practice). And I'd forgotten this 'feature' of my vimrc setup by the time I set this up for Mu.
*	3561	Kartik K. Agaram	2016-10-22	1	-2/+2
\|
*	3431	Kartik K. Agaram	2016-09-30	1	-0/+12
\| \| \| \| \|	Improvements to syntax highlighting, particularly for Mu code in C++ files.
*	1555 - mu.vim: distinguish control-flow from constants	Kartik K. Agaram	2015-06-12	1	-2/+1
\| \| \| \|	We also do this in regular C++ now.
*	1297	Kartik K. Agaram	2015-05-07	1	-5/+8
\|
*	1276 - make C++ version the default	Kartik K. Agaram	2015-05-05	1	-6/+34
\| \| \| \|	I've tried to update the Readme, but there are at least a couple of issues.
*	1150	Kartik K. Agaram	2015-04-23	1	-1/+0
\|
*	1093 - little more vim support for the old arc version	Kartik K. Agaram	2015-04-17	1	-0/+8
\|
*	744 - test cursor movement in trace browser	Kartik K. Agaram	2015-02-11	1	-0/+1
	Don't prevent run-code from clobbering existing functions, but warn because it makes traces easier to read if the different sections of a test can be distinguished.