5001 - drop the :(scenario) DSL

I've been saying for a while[1][2][3] that adding extra abstractions makes
things harder for newcomers, and adding new notations doubly so. And then
I notice this DSL in my own backyard. Makes me feel like a hypocrite.

[1] https://news.ycombinator.com/item?id=13565743#13570092
[2] https://lobste.rs/s/to8wpr/configuration_files_are_canary_warning
[3] https://lobste.rs/s/mdmcdi/little_languages_by_jon_bentley_1986#c_3miuf2

The implementation of the DSL was also highly hacky:

a) It was happening in the tangle/ tool, but was utterly unrelated to tangling
layers.

b) There were several persnickety constraints on the different kinds of
lines and the specific order they were expected in. I kept finding bugs
where the translator would silently do the wrong thing. Or the error messages
sucked, and readers may be stuck looking at the generated code to figure
out what happened. Fixing error messages would require a lot more code,
which is one of my arguments against DSLs in the first place: they may
be easy to implement, but they're hard to design to go with the grain of
the underlying platform. They require lots of iteration. Is that effort
worth prioritizing in this project?

On the other hand, the DSL did make at least some readers' life easier,
the ones who weren't immediately put off by having to learn a strange syntax.
There were fewer quotes to parse, fewer backslash escapes.

Anyway, since there are also people who dislike having to put up with strange
syntaxes, we'll call that consideration a wash and tear this DSL out.

---

This commit was sheer drudgery. Hopefully it won't need to be redone with
a new DSL because I grow sick of backslashes.

1 files changed, 0 insertions, 23 deletions

diff --git a/vimrc.vim b/vimrc.vim
index adbb9403..5eba7448 100644
--- a/vimrc.vim
+++ b/vimrc.vim
@@ -19,29 +19,6 @@ function! HighlightTangledFile()
 
   highlight Special ctermfg=160
 
-  " 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 muSalientComment /##.*$/ | highlight link muSalientComment SalientComment
-  syntax match muCommentedCode /#? .*$/ | highlight link muCommentedCode CommentedCode
-  set comments+=n:#
-  " Some other bare-bones Mu highlighting.
-  syntax match muLiteral %[^ ]\+:literal/[^ ,]*\|[^ ]\+:literal\>%
-  syntax match muLiteral %[^ ]\+:label/[^ ,]*\|[^ ]\+:label\>%
-  syntax match muLiteral %[^ ]\+:type/[^ ,]*\|[^ ]\+:type\>%
-  syntax match muLiteral %[^ ]\+:offset/[^ ,]*\|[^ ]\+:offset\>%
-  syntax match muLiteral %[^ ]\+:variant/[^ ,]*\|[^ ]\+:variant\>%
-  syntax match muLiteral % true\(\/[^ ]*\)\?\| false\(\/[^ ]*\)\?%  " literals will never be the first word in an instruction
-  syntax match muLiteral % null\(\/[^ ]*\)\?%
-  highlight link muLiteral Constant
-  syntax match muAssign " <- \|\<raw\>" | highlight link muAssign SpecialChar
-  " common keywords
-  syntax match muRecipe "^recipe\>\|^recipe!\>\|^def\>\|^def!\>\|^before\>\|^after\>\| -> " | highlight muRecipe ctermfg=208
-  syntax match muScenario "^scenario\>" | highlight muScenario ctermfg=34
-  syntax match muPendingScenario "^pending-scenario\>" | highlight link muPendingScenario SpecialChar
-  syntax match muData "^type\>\|^container\>\|^exclusive-container\>" | highlight muData ctermfg=226
-
   syntax match subxString %"[^"]*"% | highlight link subxString Constant
   " match globals but not registers like 'EAX'
   syntax match subxGlobal %\<[A-Z][a-z0-9_-]*\>% | highlight link subxGlobal SpecialChar