vim/UltiSnips
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
81f9173138
UltiSnips/syntax/snippets.vim

209 lines
9.7 KiB
VimL
Raw Normal View History

Added a syntax file by Timo Schmiade. Made sure all shipped files are recognized as snippets, even when ftdetect is not in /Users/sirver
2011-02-17 08:07:27 -05:00
" Syntax highlighting for snippet files (used for UltiSnips.vim)
Added improvements to the syntax file by Anthony Jackson
2011-03-27 02:07:44 -04:00
" Revision: 26/03/11 19:53:33
if exists("b:current_syntax")
finish
endif
Set up basic highlighting for snipmate files Try to detect a snipmate-formatted file by looking at the directory name and searching for endsnippet. If we think it's a snipmate file, switch over to an alternative syntax highlighting variant.
2014-07-01 00:14:55 -04:00
if expand("%:p:h:t") == "snippets" && search("^endsnippet", "nw") == 0
\ && !exists("b:ultisnips_override_snipmate")
" this appears to be a snipmate file
" It's in a directory called snippets/ and there's no endsnippet keyword
" anywhere in the file.
source <sfile>:h/snippets_snipmate.vim
finish
endif
Add hierarchy to syntax file Redo comments with fold markers to provide an appropriate hierarchy to the syntax file itself.
2014-06-30 02:04:37 -04:00
" Embedded Syntaxes {{{1
Ignore Errors E403 from included syntax files This will silently discard Errors raised by syntax files that are not designed to be included more than once.
2014-07-30 07:34:15 -04:00
try
syntax include @Python syntax/python.vim
unlet b:current_syntax
syntax include @Viml syntax/vim.vim
unlet b:current_syntax
syntax include @Shell syntax/sh.vim
unlet b:current_syntax
catch /E403/
" Ignore errors about syntax files that can't be loaded more than once
endtry
Added a syntax file by Timo Schmiade. Made sure all shipped files are recognized as snippets, even when ftdetect is not in /Users/sirver
2011-02-17 08:07:27 -05:00
Add hierarchy to syntax file Redo comments with fold markers to provide an appropriate hierarchy to the syntax file itself.
2014-06-30 02:04:37 -04:00
" Syntax definitions {{{1
" Comments {{{2
Mark up syntax items with 'display' as appropriate
2014-06-30 02:22:53 -04:00
syn match snipComment "^#.*" contains=snipTODO display
syn keyword snipTODO contained display FIXME NOTE NOTES TODO XXX
Added improvements to the syntax file by Anthony Jackson
2011-03-27 02:07:44 -04:00
Clean up miscellaneous syntax items Remove a few obsolete items. Remove the snipTabsOnly item. A tab-only line is not necessarily an error. Color leading spaces with a red background, because the default Error coloring doesn't affect the display of spaces.
2014-06-30 18:41:35 -04:00
" Errors {{{2
Add hierarchy to syntax file Redo comments with fold markers to provide an appropriate hierarchy to the syntax file itself.
2014-06-30 02:04:37 -04:00
Clean up miscellaneous syntax items Remove a few obsolete items. Remove the snipTabsOnly item. A tab-only line is not necessarily an error. Color leading spaces with a red background, because the default Error coloring doesn't affect the display of spaces.
2014-06-30 18:41:35 -04:00
syn match snipLeadingSpaces "^\t* \+" contained
Updated syntax file by Timo Schmiade
2011-02-19 14:00:24 -05:00
Add hierarchy to syntax file Redo comments with fold markers to provide an appropriate hierarchy to the syntax file itself.
2014-06-30 02:04:37 -04:00
" Extends {{{2
Mark up syntax items with 'display' as appropriate
2014-06-30 02:22:53 -04:00
syn match snipExtends "^extends\%(\s.*\|$\)" contains=snipExtendsKeyword display
syn match snipExtendsKeyword "^extends" contained display
Added a syntax file by Timo Schmiade. Made sure all shipped files are recognized as snippets, even when ftdetect is not in /Users/sirver
2011-02-17 08:07:27 -05:00
Add hierarchy to syntax file Redo comments with fold markers to provide an appropriate hierarchy to the syntax file itself.
2014-06-30 02:04:37 -04:00
" Definitions {{{2
" snippet {{{3
Tweak snippet/global highlighting to always highlight the end The snippet/global regions were always ending correctly, but an unclosed contained region could cause the wrong highlighting to apply to the endsnippet/endglobal. Tweak the definitions such that the snippet/global regions actually end at the start of the line and the footer occurs outside the region.
2014-06-30 22:26:28 -04:00
syn region snipSnippet start="^snippet\_s" end="^\zeendsnippet\s*$" contains=snipSnippetHeader nextgroup=snipSnippetFooter fold keepend
Fix empty snippets/globals
2014-06-30 03:00:20 -04:00
syn match snipSnippetHeader "^.*$" nextgroup=snipSnippetBody,snipSnippetFooter skipnl contained contains=snipSnippetHeaderKeyword
syn match snipSnippetHeaderKeyword "^snippet" contained nextgroup=snipSnippetTrigger skipwhite
Tweak snippet/global highlighting to always highlight the end The snippet/global regions were always ending correctly, but an unclosed contained region could cause the wrong highlighting to apply to the endsnippet/endglobal. Tweak the definitions such that the snippet/global regions actually end at the start of the line and the footer occurs outside the region.
2014-06-30 22:26:28 -04:00
syn region snipSnippetBody start="\_." end="^\zeendsnippet\s*$" contained contains=snipLeadingSpaces,@snipTokens
Rewrite syntax matching for `snippet`
2014-06-30 02:33:36 -04:00
syn match snipSnippetFooter "^endsnippet.*" contained contains=snipSnippetFooterKeyword
syn match snipSnippetFooterKeyword "^endsnippet" contained
Fix coloring of shell/VimL/Python command substitutions Include the sh syntax for shell commands. Make the matching on !v/!p work more accurately. Highlight the !v/!p separately from the embedded Python/VimL. AFAIK the only issue now is that "\`" escapes inside shell/VimL/Python are not treated as bare "`" characters by the embedded syntax, but I don't believe there's any way to fix that.
2014-06-29 23:47:22 -04:00
Syntax highlight the snippet trigger properly This supports multiword triggers, docstrings, options, and even highlights invalid multiword triggers as errors.
2014-06-30 16:38:58 -04:00
" The current parser is a bit lax about parsing. For example, given this:
" snippet foo"bar"
" it treats `foo"bar"` as the trigger. But with this:
" snippet foo"bar baz"
" it treats `foo` as the trigger and "bar baz" as the description.
" I think this is an accident. Instead, we'll assume the description must
" be surrounded by spaces. That means we'll treat
" snippet foo"bar"
" as a trigger `foo"bar"` and
" snippet foo"bar baz"
" as an attempted multiword snippet `foo"bar baz"` that is invalid.
" NB: UltiSnips parses right-to-left, which Vim doesn't support, so that makes
" the following patterns very complicated.
syn match snipSnippetTrigger "\S\+" contained nextgroup=snipSnippetDocString,snipSnippetTriggerInvalid skipwhite
" We want to match a trailing " as the start of a doc comment, but we also
" want to allow for using " as the delimiter in a multiword/pattern snippet.
" So we have to define this twice, once in the general case that matches a
" trailing " as the doc comment, and once for the case of the multiword
" delimiter using " that has more constraints
syn match snipSnippetTrigger ,\([^"[:space:]]\).\{-}\1\%(\s*$\)\@!\ze\%(\s\+"[^"]*\%("\s\+[^"[:space:]]\+\|"\)\=\)\=\s*$, contained nextgroup=snipSnippetDocString skipwhite
syn match snipSnippetTrigger ,".\{-}"\ze\%(\s\+"\%(\s*\S\)\@=[^"]*\%("\s\+[^"[:space:]]\+\|"\)\=\)\=\s*$, contained nextgroup=snipSnippetDocString skipwhite
syn match snipSnippetTriggerInvalid ,\S\@=.\{-}\S\ze\%(\s\+"[^"]*\%("\s\+[^"[:space:]]\+\s*\|"\s*\)\=\|\s*\)$, contained nextgroup=snipSnippetDocString skipwhite
syn match snipSnippetDocString ,"[^"]*\%("\ze\s*\%(\s[^"[:space:]]\+\s*\)\=\)\=$, contained nextgroup=snipSnippetOptions skipwhite
syn match snipSnippetOptions ,\S\+, contained contains=snipSnippetOptionFlag
syn match snipSnippetOptionFlag ,[biwrts], contained
Add hierarchy to syntax file Redo comments with fold markers to provide an appropriate hierarchy to the syntax file itself.
2014-06-30 02:04:37 -04:00
" Command substitution {{{4
Set up basic highlighting for snipmate files Try to detect a snipmate-formatted file by looking at the directory name and searching for endsnippet. If we think it's a snipmate file, switch over to an alternative syntax highlighting variant.
2014-07-01 00:14:55 -04:00
syn region snipCommand keepend matchgroup=snipCommandDelim start="`" skip="\\[{}\\$`]" end="`" contained contains=snipPythonCommand,snipVimLCommand,snipShellCommand,snipCommandSyntaxOverride
Fix coloring of shell/VimL/Python command substitutions Include the sh syntax for shell commands. Make the matching on !v/!p work more accurately. Highlight the !v/!p separately from the embedded Python/VimL. AFAIK the only issue now is that "\`" escapes inside shell/VimL/Python are not treated as bare "`" characters by the embedded syntax, but I don't believe there's any way to fix that.
2014-06-29 23:47:22 -04:00
syn region snipShellCommand start="\ze\_." skip="\\[{}\\$`]" end="\ze`" contained contains=@Shell
syn region snipPythonCommand matchgroup=snipPythonCommandP start="`\@<=!p\_s" skip="\\[{}\\$`]" end="\ze`" contained contains=@Python
syn region snipVimLCommand matchgroup=snipVimLCommandV start="`\@<=!v\_s" skip="\\[{}\\$`]" end="\ze`" contained contains=@Viml
Rewrite parsing for tab stops
2014-06-30 22:15:56 -04:00
syn cluster snipTokens add=snipCommand
Set up basic highlighting for snipmate files Try to detect a snipmate-formatted file by looking at the directory name and searching for endsnippet. If we think it's a snipmate file, switch over to an alternative syntax highlighting variant.
2014-07-01 00:14:55 -04:00
syn cluster snipTabStopTokens add=snipCommand
Fix coloring of shell/VimL/Python command substitutions Include the sh syntax for shell commands. Make the matching on !v/!p work more accurately. Highlight the !v/!p separately from the embedded Python/VimL. AFAIK the only issue now is that "\`" escapes inside shell/VimL/Python are not treated as bare "`" characters by the embedded syntax, but I don't believe there's any way to fix that.
2014-06-29 23:47:22 -04:00
Stop embedding python/viml/sh if the `` includes { In order to handle brace balancing properly, we need our own region to match the {/} pairs, which unfortunately means that if a { occurs in a command substitution, we have to disable the embedded language highlighting.
2014-06-30 23:10:42 -04:00
" unfortunately due to the balanced braces parsing of commands, if a { occurs
" in the command, we need to prevent the embedded syntax highlighting.
" Otherwise, we can't track the balanced braces properly.
syn region snipCommandSyntaxOverride start="\%(\\[{}\\$`]\|\_[^`"{]\)*\ze{" skip="\\[{}\\$`]" end="\ze`" contained contains=snipBalancedBraces transparent
Rewrite parsing for tab stops
2014-06-30 22:15:56 -04:00
" Tab Stops {{{4
Add hierarchy to syntax file Redo comments with fold markers to provide an appropriate hierarchy to the syntax file itself.
2014-06-30 02:04:37 -04:00
Rewrite parsing for tab stops
2014-06-30 22:15:56 -04:00
syn match snipEscape "\\[{}\\$`]" contained
syn cluster snipTokens add=snipEscape
Set up basic highlighting for snipmate files Try to detect a snipmate-formatted file by looking at the directory name and searching for endsnippet. If we think it's a snipmate file, switch over to an alternative syntax highlighting variant.
2014-07-01 00:14:55 -04:00
syn cluster snipTabStopTokens add=snipEscape
Rewrite parsing for tab stops
2014-06-30 22:15:56 -04:00
syn match snipMirror "\$\d\+" contained
syn cluster snipTokens add=snipMirror
Set up basic highlighting for snipmate files Try to detect a snipmate-formatted file by looking at the directory name and searching for endsnippet. If we think it's a snipmate file, switch over to an alternative syntax highlighting variant.
2014-07-01 00:14:55 -04:00
syn cluster snipTabStopTokens add=snipMirror
Rewrite parsing for tab stops
2014-06-30 22:15:56 -04:00
Fix highlighting of nested tab stops Nested tab stops like `${1:head ${2} tail}` were not properly highlighting the "tail" or the closing `}` of the outer tab stop.
2014-08-05 20:21:35 -04:00
syn region snipTabStop matchgroup=snipTabStop start="\${\d\+[:}]\@=" end="}" contained contains=snipTabStopDefault extend
Set up basic highlighting for snipmate files Try to detect a snipmate-formatted file by looking at the directory name and searching for endsnippet. If we think it's a snipmate file, switch over to an alternative syntax highlighting variant.
2014-07-01 00:14:55 -04:00
syn region snipTabStopDefault matchgroup=snipTabStop start=":" skip="\\[{}]" end="\ze}" contained contains=snipTabStopEscape,snipBalancedBraces,@snipTabStopTokens keepend
Rewrite parsing for tab stops
2014-06-30 22:15:56 -04:00
syn match snipTabStopEscape "\\[{}]" contained
Stop embedding python/viml/sh if the `` includes { In order to handle brace balancing properly, we need our own region to match the {/} pairs, which unfortunately means that if a { occurs in a command substitution, we have to disable the embedded language highlighting.
2014-06-30 23:10:42 -04:00
syn region snipBalancedBraces start="{" end="}" contained transparent extend
Rewrite parsing for tab stops
2014-06-30 22:15:56 -04:00
syn cluster snipTokens add=snipTabStop
Set up basic highlighting for snipmate files Try to detect a snipmate-formatted file by looking at the directory name and searching for endsnippet. If we think it's a snipmate file, switch over to an alternative syntax highlighting variant.
2014-07-01 00:14:55 -04:00
syn cluster snipTabStopTokens add=snipTabStop
Rewrite parsing for tab stops
2014-06-30 22:15:56 -04:00
syn region snipVisual matchgroup=snipVisual start="\${VISUAL[:}/]\@=" end="}" contained contains=snipVisualDefault,snipTransformationPattern
syn region snipVisualDefault matchgroup=snipVisual start=":" end="\ze[}/]" contained contains=snipTabStopEscape nextgroup=snipTransformationPattern
syn cluster snipTokens add=snipVisual
Set up basic highlighting for snipmate files Try to detect a snipmate-formatted file by looking at the directory name and searching for endsnippet. If we think it's a snipmate file, switch over to an alternative syntax highlighting variant.
2014-07-01 00:14:55 -04:00
syn cluster snipTabStopTokens add=snipVisual
Rewrite parsing for tab stops
2014-06-30 22:15:56 -04:00
syn region snipTransformation matchgroup=snipTransformation start="\${\d\/\@=" end="}" contained contains=snipTransformationPattern
syn region snipTransformationPattern matchgroup=snipTransformationPatternDelim start="/" end="\ze/" contained contains=snipTransformationEscape nextgroup=snipTransformationReplace skipnl
syn region snipTransformationReplace matchgroup=snipTransformationPatternDelim start="/" end="/" contained contains=snipTransformationEscape nextgroup=snipTransformationOptions skipnl
syn region snipTransformationOptions start="\ze[^}]" end="\ze}" contained contains=snipTabStopEscape
syn match snipTransformationEscape "\\/" contained
syn cluster snipTokens add=snipTransformation
Set up basic highlighting for snipmate files Try to detect a snipmate-formatted file by looking at the directory name and searching for endsnippet. If we think it's a snipmate file, switch over to an alternative syntax highlighting variant.
2014-07-01 00:14:55 -04:00
syn cluster snipTabStopTokens add=snipTransformation
Added a syntax file by Timo Schmiade. Made sure all shipped files are recognized as snippets, even when ftdetect is not in /Users/sirver
2011-02-17 08:07:27 -05:00
Add hierarchy to syntax file Redo comments with fold markers to provide an appropriate hierarchy to the syntax file itself.
2014-06-30 02:04:37 -04:00
" global {{{3
Rewrite syntax matching for `global` The body of a global now only has Python syntax coloring if the trigger is !p. This matches the actual behavior of UltiSnips. AFAIK right now globals with other triggers are useless, but this opens the door to proper syntax coloring for those if they ever gain a use.
2014-06-30 02:44:22 -04:00
" Generic (non-Python) {{{4
Fix empty snippets/globals
2014-06-30 03:00:20 -04:00
Tweak snippet/global highlighting to always highlight the end The snippet/global regions were always ending correctly, but an unclosed contained region could cause the wrong highlighting to apply to the endsnippet/endglobal. Tweak the definitions such that the snippet/global regions actually end at the start of the line and the footer occurs outside the region.
2014-06-30 22:26:28 -04:00
syn region snipGlobal start="^global\_s" end="^\zeendglobal\s*$" contains=snipGlobalHeader nextgroup=snipGlobalFooter fold keepend
Fix empty snippets/globals
2014-06-30 03:00:20 -04:00
syn match snipGlobalHeader "^.*$" nextgroup=snipGlobalBody,snipGlobalFooter skipnl contained contains=snipGlobalHeaderKeyword
Tweak snippet/global highlighting to always highlight the end The snippet/global regions were always ending correctly, but an unclosed contained region could cause the wrong highlighting to apply to the endsnippet/endglobal. Tweak the definitions such that the snippet/global regions actually end at the start of the line and the footer occurs outside the region.
2014-06-30 22:26:28 -04:00
syn region snipGlobalBody start="\_." end="^\zeendglobal\s*$" contained contains=snipLeadingSpaces
Rewrite syntax matching for `global` The body of a global now only has Python syntax coloring if the trigger is !p. This matches the actual behavior of UltiSnips. AFAIK right now globals with other triggers are useless, but this opens the door to proper syntax coloring for those if they ever gain a use.
2014-06-30 02:44:22 -04:00
" Python (!p) {{{4
Tweak snippet/global highlighting to always highlight the end The snippet/global regions were always ending correctly, but an unclosed contained region could cause the wrong highlighting to apply to the endsnippet/endglobal. Tweak the definitions such that the snippet/global regions actually end at the start of the line and the footer occurs outside the region.
2014-06-30 22:26:28 -04:00
syn region snipGlobal start=,^global\s\+!p\%(\s\+"[^"]*\%("\s\+[^"[:space:]]\+\|"\)\=\)\=\s*$, end=,^\zeendglobal\s*$, contains=snipGlobalPHeader nextgroup=snipGlobalFooter fold keepend
Fix empty snippets/globals
2014-06-30 03:00:20 -04:00
syn match snipGlobalPHeader "^.*$" nextgroup=snipGlobalPBody,snipGlobalFooter skipnl contained contains=snipGlobalHeaderKeyword
syn match snipGlobalHeaderKeyword "^global" contained nextgroup=snipSnippetTrigger skipwhite
Tweak snippet/global highlighting to always highlight the end The snippet/global regions were always ending correctly, but an unclosed contained region could cause the wrong highlighting to apply to the endsnippet/endglobal. Tweak the definitions such that the snippet/global regions actually end at the start of the line and the footer occurs outside the region.
2014-06-30 22:26:28 -04:00
syn region snipGlobalPBody start="\_." end="^\zeendglobal\s*$" contained contains=@Python
Added a syntax file by Timo Schmiade. Made sure all shipped files are recognized as snippets, even when ftdetect is not in /Users/sirver
2011-02-17 08:07:27 -05:00
Fix empty snippets/globals
2014-06-30 03:00:20 -04:00
" Common {{{4
syn match snipGlobalFooter "^endglobal.*" contained contains=snipGlobalFooterKeyword
syn match snipGlobalFooterKeyword "^endglobal" contained
Add hierarchy to syntax file Redo comments with fold markers to provide an appropriate hierarchy to the syntax file itself.
2014-06-30 02:04:37 -04:00
" priority {{{3
Mark up syntax items with 'display' as appropriate
2014-06-30 02:22:53 -04:00
syn match snipPriority "^priority\%(\s.*\|$\)" contains=snipPriorityKeyword display
syn match snipPriorityKeyword "^priority" contained nextgroup=snipPriorityValue skipwhite display
syn match snipPriorityValue "-\?\d\+" contained display
Syntaxhighlighting for clearsnippets by Aaron Schrab
2012-11-24 04:12:36 -05:00
Add hierarchy to syntax file Redo comments with fold markers to provide an appropriate hierarchy to the syntax file itself.
2014-06-30 02:04:37 -04:00
" Snippt Clearing {{{2
Mark up syntax items with 'display' as appropriate
2014-06-30 02:22:53 -04:00
syn match snipClear "^clearsnippets\%(\s.*\|$\)" contains=snipClearKeyword display
syn match snipClearKeyword "^clearsnippets" contained display
Add hierarchy to syntax file Redo comments with fold markers to provide an appropriate hierarchy to the syntax file itself.
2014-06-30 02:04:37 -04:00
" Highlight groups {{{1
Added a syntax file by Timo Schmiade. Made sure all shipped files are recognized as snippets, even when ftdetect is not in /Users/sirver
2011-02-17 08:07:27 -05:00
Fix highlighting of Python/VimL commands Also mark all the highlighting as default, so it can be overridden more easily by the user.
2014-06-29 22:36:07 -04:00
hi def link snipComment Comment
fixup! Clean up miscellaneous syntax items
2014-06-30 21:38:50 -04:00
hi def link snipTODO Todo
Clean up miscellaneous syntax items Remove a few obsolete items. Remove the snipTabsOnly item. A tab-only line is not necessarily an error. Color leading spaces with a red background, because the default Error coloring doesn't affect the display of spaces.
2014-06-30 18:41:35 -04:00
hi def snipLeadingSpaces term=reverse ctermfg=15 ctermbg=4 gui=reverse guifg=#dc322f
Updated syntax file by Timo Schmiade
2011-02-19 14:00:24 -05:00
Fix highlighting of Python/VimL commands Also mark all the highlighting as default, so it can be overridden more easily by the user.
2014-06-29 22:36:07 -04:00
hi def link snipKeyword Keyword
Added a syntax file by Timo Schmiade. Made sure all shipped files are recognized as snippets, even when ftdetect is not in /Users/sirver
2011-02-17 08:07:27 -05:00
Rewrite syntax matching for `global` The body of a global now only has Python syntax coloring if the trigger is !p. This matches the actual behavior of UltiSnips. AFAIK right now globals with other triggers are useless, but this opens the door to proper syntax coloring for those if they ever gain a use.
2014-06-30 02:44:22 -04:00
hi def link snipExtendsKeyword snipKeyword
Added a syntax file by Timo Schmiade. Made sure all shipped files are recognized as snippets, even when ftdetect is not in /Users/sirver
2011-02-17 08:07:27 -05:00
Rewrite syntax matching for `snippet`
2014-06-30 02:33:36 -04:00
hi def link snipSnippetHeaderKeyword snipKeyword
hi def link snipSnippetFooterKeyword snipKeyword
Syntax highlight the snippet trigger properly This supports multiword triggers, docstrings, options, and even highlights invalid multiword triggers as errors.
2014-06-30 16:38:58 -04:00
hi def link snipSnippetTrigger Identifier
hi def link snipSnippetTriggerInvalid Error
hi def link snipSnippetDocString String
hi def link snipSnippetOptionFlag Special
Rewrite syntax matching for `global` The body of a global now only has Python syntax coloring if the trigger is !p. This matches the actual behavior of UltiSnips. AFAIK right now globals with other triggers are useless, but this opens the door to proper syntax coloring for those if they ever gain a use.
2014-06-30 02:44:22 -04:00
hi def link snipGlobalHeaderKeyword snipKeyword
hi def link snipGlobalFooterKeyword snipKeyword
Fix coloring of shell/VimL/Python command substitutions Include the sh syntax for shell commands. Make the matching on !v/!p work more accurately. Highlight the !v/!p separately from the embedded Python/VimL. AFAIK the only issue now is that "\`" escapes inside shell/VimL/Python are not treated as bare "`" characters by the embedded syntax, but I don't believe there's any way to fix that.
2014-06-29 23:47:22 -04:00
Fix highlighting of Python/VimL commands Also mark all the highlighting as default, so it can be overridden more easily by the user.
2014-06-29 22:36:07 -04:00
hi def link snipCommand Special
Fix coloring of shell/VimL/Python command substitutions Include the sh syntax for shell commands. Make the matching on !v/!p work more accurately. Highlight the !v/!p separately from the embedded Python/VimL. AFAIK the only issue now is that "\`" escapes inside shell/VimL/Python are not treated as bare "`" characters by the embedded syntax, but I don't believe there's any way to fix that.
2014-06-29 23:47:22 -04:00
hi def link snipCommandDelim snipCommand
hi def link snipShellCommand snipCommand
Fix highlighting of Python/VimL commands Also mark all the highlighting as default, so it can be overridden more easily by the user.
2014-06-29 22:36:07 -04:00
hi def link snipVimLCommand snipCommand
Fix coloring of shell/VimL/Python command substitutions Include the sh syntax for shell commands. Make the matching on !v/!p work more accurately. Highlight the !v/!p separately from the embedded Python/VimL. AFAIK the only issue now is that "\`" escapes inside shell/VimL/Python are not treated as bare "`" characters by the embedded syntax, but I don't believe there's any way to fix that.
2014-06-29 23:47:22 -04:00
hi def link snipPythonCommandP PreProc
hi def link snipVimLCommandV PreProc
Rewrite parsing for tab stops
2014-06-30 22:15:56 -04:00
hi def link snipEscape Special
hi def link snipMirror StorageClass
hi def link snipTabStop Define
hi def link snipTabStopDefault String
hi def link snipTabStopEscape Special
hi def link snipVisual snipTabStop
hi def link snipVisualDefault snipTabStopDefault
hi def link snipTransformation snipTabStop
hi def link snipTransformationPattern String
hi def link snipTransformationPatternDelim Operator
hi def link snipTransformationReplace String
hi def link snipTransformationEscape snipEscape
hi def link snipTransformationOptions Operator
Added a syntax file by Timo Schmiade. Made sure all shipped files are recognized as snippets, even when ftdetect is not in /Users/sirver
2011-02-17 08:07:27 -05:00
Rewrite extends/priority/clearsnippets
2014-06-30 02:11:11 -04:00
hi def link snipPriorityKeyword Keyword
hi def link snipPriorityValue Number
hi def link snipClearKeyword Keyword
Syntaxhighlighting for clearsnippets by Aaron Schrab
2012-11-24 04:12:36 -05:00
Add hierarchy to syntax file Redo comments with fold markers to provide an appropriate hierarchy to the syntax file itself.
2014-06-30 02:04:37 -04:00
" }}}1
Fix syntax name b:current_syntax should be set to "snippets", as that's the filetype, not "snippet".
2014-06-29 22:42:57 -04:00
let b:current_syntax = "snippets"
Reference in New Issue Copy Permalink