Mercurial > vim
view runtime/syntax/cweb.vim @ 28938:ddbb36c1830b v8.2.4991
patch 8.2.4991: no test for hwat patch 8.1.0535 fixes
Commit: https://github.com/vim/vim/commit/93c1573dd284dc9cf5ed9265a0143aaf520d2920
Author: zeertzjq <zeertzjq@outlook.com>
Date: Sat May 21 16:34:38 2022 +0100
patch 8.2.4991: no test for hwat patch 8.1.0535 fixes
Problem: No test for hwat patch 8.1.0535 fixes.
Solution: Add a test. (closes https://github.com/vim/vim/issues/10462)
author | Bram Moolenaar <Bram@vim.org> |
---|---|
date | Sat, 21 May 2022 17:45:03 +0200 |
parents | 46763b01cd9a |
children |
line wrap: on
line source
" Vim syntax file " Language: CWEB " Maintainer: Andreas Scherer <andreas.scherer@pobox.com> " 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 <sfile>: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 <someone@@fsf.org> 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