Mercurial > vim
view runtime/syntax/cweb.vim @ 2994:7f4f5ca70dbd v7.3.269
updated for version 7.3.269
Problem: 'shellcmdflag' only works with one flag.
Solution: Split into multiple arguments. (Gary Johnson)
author | Bram Moolenaar <bram@vim.org> |
---|---|
date | Thu, 04 Aug 2011 22:59:28 +0200 |
parents | 3fc0f57ecb91 |
children | 91e53bcb7946 |
line wrap: on
line source
" Vim syntax file " Language: CWEB " Maintainer: Andreas Scherer <andreas.scherer@pobox.com> " Last Change: April 30, 2001 " 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.) " For version 5.x: Clear all syntax items " For version 6.x: Quit when a syntax file was already loaded if version < 600 syntax clear elseif 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. if version < 600 source <sfile>:p:h/tex.vim else runtime! syntax/tex.vim unlet b:current_syntax endif " 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 <sfile>:p:h/cpp.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 <someone@@fsf.org> without going into C/C++ mode.) syntax match webIgnoredStuff "@@" " Define the default highlighting. " For version 5.7 and earlier: only when not done already " For version 5.8 and later: only when an item doesn't have highlighting yet if version >= 508 || !exists("did_cweb_syntax_inits") if version < 508 let did_cweb_syntax_inits = 1 command -nargs=+ HiLink hi link <args> else command -nargs=+ HiLink hi def link <args> endif HiLink webRestrictedTeX String delcommand HiLink endif let b:current_syntax = "cweb" " vim: ts=8