blob: eae812c94d8279a30d7a7681ee1e3866bf7820ba (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
|
" Highlighting literate directives in C++ sources.
function! HighlightTangledFile()
if &ft == "" || &ft == "cpp"
set ft=cpp
endif
set comments-=://
set comments-=n://
set comments+=n://:,n://
set isk+=-
syntax region tangleDirective start=+:(+ skip=+".*"+ end=+)+
highlight link tangleDirective Delimiter
syntax region traceContains start="^+" end="$"
highlight traceContains ctermfg=darkgreen
syntax region traceAbsent start="^-" end="$"
highlight traceAbsent ctermfg=darkred
" 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
" Tangled comments only make sense in the sources and are stripped out of
" the generated .cc file. They're highlighted same as regular comments.
syntax match tangledComment /\/\/:.*/ | highlight link tangledComment Comment
syntax match tangledSalientComment /\/\/::.*/ | highlight link tangledSalientComment SalientComment
endfunction
call HighlightTangledFile()
autocmd BufRead,BufNewFile *.mu set ft=mu
autocmd BufRead,BufNewFile 0* call HighlightTangledFile()
" Scenarios considered:
" opening or starting vim with a new or existing file without an extension (should interpret as C++)
" opening or starting vim with a new or existing file with a .mu extension
" starting vim or opening a buffer without a file name (ok to do nothing)
" opening a second file in a new or existing window (shouldn't mess up existing highlighting)
" reloading an existing file (shouldn't mess up existing highlighting)
|