vim-glsl.git/after, branch master Vim runtime files for OpenGL Shading Language https://git.agrajag.net/vim-glsl.git/atom?h=master 2022-02-06T15:41:49Z Update my name and email 2022-02-06T15:41:49Z Sergii Tykhomyrov sergii@tykhomyrov.com 2022-02-06T15:41:49Z urn:sha1:42ffed856d5d156ec0f9c12233be34182cbb08ea Add shader source syntax highlighting in Elm 2020-04-21T07:35:21Z Sergey Tikhomirov sergey@tikhomirov.io 2020-04-21T07:35:21Z urn:sha1:36266238d96cd2219769793855a7e915f5e6a32c Added containedin=javaScript to html syntax region (#17) 2019-11-01T08:22:34Z Auxiliary-Character auxchar@gmail.com 2019-11-01T08:22:34Z urn:sha1:fbdb226318e3e1747b29f31ad07c0cce07e9f22a 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. Add syntax highlighting for WebGL shaders in <script> tags 2014-02-09T14:10:13Z Sergey Tikhomirov sergey@tikhomirov.io 2014-02-09T14:10:13Z urn:sha1:b62d69dcf6d03ff1317f111a2a035ad0b0374d56