diff options
| author | Auxiliary-Character <auxchar@gmail.com> | 2019-11-01 03:22:34 -0500 |
|---|---|---|
| committer | Sergey Tikhomirov <sergey@tikhomirov.io> | 2019-11-01 09:22:34 +0100 |
| commit | fbdb226318e3e1747b29f31ad07c0cce07e9f22a (patch) | |
| tree | 110546474d6424c2fc88ddf2f2b76444693896a7 /syntax/glsl.vim | |
| parent | 697eca9784ffac39308e1fd45e0300582c3d060b (diff) | |
| download | vim-glsl-fbdb226318e3e1747b29f31ad07c0cce07e9f22a.tar.gz vim-glsl-fbdb226318e3e1747b29f31ad07c0cce07e9f22a.zip | |
Added containedin=javaScript to html syntax region (#17)
I was suprised to find when I started digging that this plugin already
has a syntax region for html, since it didn't actually work for me.
After investigating what was going on using
[this](https://vim.fandom.com/wiki/Identify_the_syntax_highlighting_group_used_at_the_cursor),
I came to the realization that the html plugin was already highlighting
the content within script tags as JavaScript, and that this was taking
priority over glsl highlighting that this plugin does.
Well, according to [this StackOverflow
answer](https://vim.fandom.com/wiki/Identify_the_syntax_highlighting_group_used_at_the_cursor),
you can beat such priority conflicts by telling vim that this group
(`ShaderScript`) `containedin` another group (`javaScript`). This
appears to have solved the problem for me.
Diffstat (limited to 'syntax/glsl.vim')
0 files changed, 0 insertions, 0 deletions