Skip to content

Commit 4f5e03d

Browse files
committed
Using runtime over syntax include
syntax include has a sort of sugar to it that forces all sourced highlighting to be contained, this will break certain more general highlighting for jsFlow. runtime on the other hand, works exactly as you'd expect.
1 parent dce4de2 commit 4f5e03d

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

syntax/javascript.vim

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -193,15 +193,15 @@ syntax region jsEnvComment start="\%^#!" end="$" display
193193
syntax region jsCvsTag contained start="\$\cid:" end="\$" oneline
194194

195195
if !exists("javascript_ignore_javaScriptdoc")
196-
syntax include extras/jsdocs.vim
196+
runtime extras/jsdocs.vim
197197
endif
198198

199199
if exists("javascript_plugin_flow")
200-
syntax include extras/flow.vim
200+
runtime extras/flow.vim
201201
endif
202202

203203
if exists("javascript_plugin_ngdocs")
204-
syntax include extras/ngdocs.vim
204+
runtime extras/ngdocs.vim
205205
endif
206206

207207
syntax cluster jsExpression contains=jsBracket,jsParen,jsObject,jsBlock,jsTernaryIf,jsTaggedTemplate,jsTemplateString,jsString,jsRegexpString,jsNumber,jsFloat,jsOperator,jsBooleanTrue,jsBooleanFalse,jsNull,jsFunction,jsArrowFunction,jsGlobalObjects,jsExceptions,jsFutureKeys,jsDomErrNo,jsDomNodeConsts,jsHtmlEvents,jsFuncCall,jsUndefined,jsNan,jsPrototype,jsBuiltins,jsNoise,jsClassDefinition,jsArrowFunction,jsArrowFuncArgs,jsParensError,jsComment,jsArguments,jsThis,jsSuper

0 commit comments

Comments
 (0)