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

132 lines
5.0 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
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
Added improvements to the syntax file by Anthony Jackson
2011-03-27 02:07:44 -04:00
syntax include @Python syntax/python.vim
Fix embedded VimL highlighting The b:current_syntax variable is set by syntax-include, so it needs to be unset again or the second syntax-include does nothing.
2014-06-29 22:42:11 -04:00
unlet b:current_syntax
Some improvements to Syntax highlighting including support for ${VISUAL}
2012-02-05 07:15:25 -05:00
syntax include @Viml syntax/vim.vim
Fix embedded VimL highlighting The b:current_syntax variable is set by syntax-include, so it needs to be unset again or the second syntax-include does nothing.
2014-06-29 22:42:11 -04:00
unlet b:current_syntax
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 include @Shell syntax/sh.vim
unlet b:current_syntax
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
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
" Miscellaneous {{{2
Improvements to the syntax file.
2013-03-21 06:32:17 -04:00
syn match snipDocString '"[^"]*"$'
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
syn match snipString '"[^"]*"'
syn match snipTabsOnly "^\t\+$"
Added syntax highlighting for leading spaces, as they are most likely wrong.
2014-02-18 12:57:43 -05:00
syn match snipLeadingSpaces "^\t* \+"
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
Adds 'priority' keyword and removes '!' option.
2014-02-19 15:04:52 -05:00
syn match snipKeyword "\(\<\(end\)\?\(snippet\|global\)\>\)\|extends\|clearsnippets\|priority" 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
Rewrite syntax matching for `snippet`
2014-06-30 02:33:36 -04:00
syn region snipSnippet start="^snippet\_s" end="^endsnippet\s*$" contains=snipSnippetHeader 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
Rewrite syntax matching for `snippet`
2014-06-30 02:33:36 -04:00
syn region snipSnippetBody start="\_." end="^\zeendsnippet\s*$" contained contains=snipTabsOnly,snipLeadingSpaces,snipCommand,snipVarExpansion,snipVar,snipVisual nextgroup=snipSnippetFooter
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
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
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 snipCommand keepend matchgroup=snipCommandDelim start="`" skip="\\[{}\\$`]" end="`" contains=snipPythonCommand,snipVimLCommand,snipShellCommand
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
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
" Variables {{{4
improve snipVar matches, like 10 100 etc
2012-08-12 08:05:29 -04:00
syn match snipVar "\$\d*" contained
Some improvements to Syntax highlighting including support for ${VISUAL}
2012-02-05 07:15:25 -05:00
syn region snipVisual matchgroup=Define start="\${VISUAL" end="}" contained
improve snipVar matches, like 10 100 etc
2012-08-12 08:05:29 -04:00
syn region snipVarExpansion matchgroup=Define start="\${\d*" end="}" contained contains=snipVar,snipVarExpansion,snipCommand
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
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
syn region snipGlobal start="^global\_s" end="^endglobal\s*$" contains=snipGlobalHeader fold keepend
Fix empty snippets/globals
2014-06-30 03:00:20 -04:00
syn match snipGlobalHeader "^.*$" nextgroup=snipGlobalBody,snipGlobalFooter skipnl contained contains=snipGlobalHeaderKeyword
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
syn region snipGlobalBody start="\_." end="^\zeendglobal\s*$" contained contains=snipTabsOnly,snipLeadingSpaces nextgroup=snipGlobalFooter
" Python (!p) {{{4
syn region snipGlobal start="^global\s\+!p\_s\@=" end="^endglobal\s*$" contains=snipGlobalPHeader 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
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
syn region snipGlobalPBody start="\_." end="^\zeendglobal\s*$" contained contains=snipTabsOnly,snipLeadingSpaces,@Python nextgroup=snipGlobalFooter
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
hi def link snipLeadingSpaces Error
hi def link snipString String
hi def link snipDocString String
hi def link snipTabsOnly Error
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
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 snipPythonCommand snipCommand
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
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 snipVar StorageClass
hi def link snipVarExpansion Normal
hi def link snipVisual Normal
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
hi def link snipSnippet Normal
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