diff options
| author | Kartik K. Agaram <vc@akkartik.com> | 2015-10-28 18:19:41 -0700 |
|---|---|---|
| committer | Kartik K. Agaram <vc@akkartik.com> | 2015-10-28 18:26:05 -0700 |
| commit | 70f70118f468b51ac14b7e992b0ec941c3a50d4d (patch) | |
| tree | 07749a54af09d9bfbeb93b7b52dc4a175ed6a886 /mu.vim | |
| parent | b69daf785df8dee56f851ce9d6dd38d7779a04ca (diff) | |
| download | mu-70f70118f468b51ac14b7e992b0ec941c3a50d4d.tar.gz | |
2306 - recipe headers
Once a student has gotten used to recipes and ingredients using the staged 'next-ingredient' approach there's no reason to avoid conventional function headers. As an added bonus we can now: a) check that all 'reply' instructions in a recipe are consistent b) deduce what to reply without needing to say so everytime c) start thinking about type parameters for recipes (generic functions!)
Diffstat (limited to 'mu.vim')
| -rw-r--r-- | mu.vim | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/mu.vim b/mu.vim index 72255940..bb77b50d 100644 --- a/mu.vim +++ b/mu.vim @@ -62,6 +62,7 @@ syntax match muGlobal %[^ ]\+:global/\?[^ ,]*% | highlight link muGlobal Special syntax keyword muControl reply reply-if reply-unless jump jump-if jump-unless loop loop-if loop-unless break break-if break-unless current-continuation continue-from create-delimited-continuation reply-delimited-continuation | highlight muControl ctermfg=3 " common keywords syntax keyword muRecipe recipe recipe! before after | highlight muRecipe ctermfg=208 +syntax match muRecipe " -> " syntax keyword muScenario scenario | highlight muScenario ctermfg=34 syntax keyword muData container exclusive-container | highlight muData ctermfg=226 |