From 029f72b1a93430b24b88eb3a72c6114d9f149737 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Wed, 10 Apr 2024 22:09:20 +0200 Subject: Adding upstream version 2:9.1.0016. Signed-off-by: Daniel Baumann --- runtime/syntax/cweb.vim | 68 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 68 insertions(+) create mode 100644 runtime/syntax/cweb.vim (limited to 'runtime/syntax/cweb.vim') diff --git a/runtime/syntax/cweb.vim b/runtime/syntax/cweb.vim new file mode 100644 index 0000000..4e06b36 --- /dev/null +++ b/runtime/syntax/cweb.vim @@ -0,0 +1,68 @@ +" Vim syntax file +" Language: CWEB +" Maintainer: Andreas Scherer +" Last Change: 2011 Dec 25 by Thilo Six + +" Details of the CWEB language can be found in the article by Donald E. Knuth +" and Silvio Levy, "The CWEB System of Structured Documentation", included as +" file "cwebman.tex" in the standard CWEB distribution, available for +" anonymous ftp at ftp://labrea.stanford.edu/pub/cweb/. + +" TODO: Section names and C/C++ comments should be treated as TeX material. +" TODO: The current version switches syntax highlighting off for section +" TODO: names, and leaves C/C++ comments as such. (On the other hand, +" TODO: switching to TeX mode in C/C++ comments might be colour overkill.) + +" quit when a syntax file was already loaded +if exists("b:current_syntax") + finish +endif + +" For starters, read the TeX syntax; TeX syntax items are allowed at the top +" level in the CWEB syntax, e.g., in the preamble. In general, a CWEB source +" code can be seen as a normal TeX document with some C/C++ material +" interspersed in certain defined regions. +runtime! syntax/tex.vim +unlet b:current_syntax + +" Read the C/C++ syntax too; C/C++ syntax items are treated as such in the +" C/C++ section of a CWEB chunk or in inner C/C++ context in "|...|" groups. +syntax include @webIncludedC :p:h/cpp.vim + +let s:cpo_save = &cpo +set cpo&vim + +" Inner C/C++ context (ICC) should be quite simple as it's comprised of +" material in "|...|"; however the naive definition for this region would +" hickup at the innocious "\|" TeX macro. Note: For the time being we expect +" that an ICC begins either at the start of a line or after some white space. +syntax region webInnerCcontext start="\(^\|[ \t\~`(]\)|" end="|" contains=@webIncludedC,webSectionName,webRestrictedTeX,webIgnoredStuff + +" Genuine C/C++ material. This syntactic region covers both the definition +" part and the C/C++ part of a CWEB section; it is ended by the TeX part of +" the next section. +syntax region webCpart start="@[dfscp<(]" end="@[ \*]" contains=@webIncludedC,webSectionName,webRestrictedTeX,webIgnoredStuff + +" Section names contain C/C++ material only in inner context. +syntax region webSectionName start="@[<(]" end="@>" contains=webInnerCcontext contained + +" The contents of "control texts" is not treated as TeX material, because in +" non-trivial cases this completely clobbers the syntax recognition. Instead, +" we highlight these elements as "strings". +syntax region webRestrictedTeX start="@[\^\.:t=q]" end="@>" oneline + +" Double-@ means single-@, anywhere in the CWEB source. (This allows e-mail +" address without going into C/C++ mode.) +syntax match webIgnoredStuff "@@" + +" Define the default highlighting. +" Only when an item doesn't have highlighting yet + +hi def link webRestrictedTeX String + + +let b:current_syntax = "cweb" + +let &cpo = s:cpo_save +unlet s:cpo_save +" vim: ts=8 -- cgit v1.2.3