diff options
author | Kartik K. Agaram <vc@akkartik.com> | 2016-12-12 10:01:12 -0800 |
---|---|---|
committer | Kartik K. Agaram <vc@akkartik.com> | 2016-12-12 10:07:59 -0800 |
commit | 49620728e805a3bbc3477c14b8b6ef7e2b5d3ead (patch) | |
tree | c80ecf970ec78dfc0c40944a4b9e827c0eb77078 /vimrc.vim | |
parent | d81fcff20567a1d5e793e813bc761222885660b1 (diff) | |
download | mu-49620728e805a3bbc3477c14b8b6ef7e2b5d3ead.tar.gz |
3707
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.)
Diffstat (limited to 'vimrc.vim')
-rw-r--r-- | vimrc.vim | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/vimrc.vim b/vimrc.vim index 83cc29b8..5587637e 100644 --- a/vimrc.vim +++ b/vimrc.vim @@ -19,7 +19,9 @@ function! HighlightTangledFile() " Our C++ files can have Mu code in scenarios, so highlight Mu comments like " regular comments. - syntax match muComment /# .*$/ | highlight link muComment Comment + syntax match muComment /# .*$/ + syntax match muComment /#: .*$/ + highlight link muComment Comment syntax match muSalientComment /##.*$/ | highlight link muSalientComment SalientComment syntax match muCommentedCode /#? .*$/ | highlight link muCommentedCode CommentedCode set comments+=n:# |