You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I edit *.comp files as GLSL compute shaders, and was rather surprised when they were not highlighted properly due to having mason filetype.
The workaround is to add perl into polyglot_disable global variable, as mason registration happens under "perl is not disabled" condition.
But I wonder what is a proper way to fix it.
Is *.comp even a valid/common file extension for mason, whatever that is?
More collisions can be expected (e.g. racket scheme filetype collision #670). Is there a reasonable way to disambiguate those without disabling support for whole languages?
The text was updated successfully, but these errors were encountered:
mason
:vim-polyglot/autoload/polyglot/init.vim
Line 2221 in bc8a81d
glsl
:vim-polyglot/autoload/polyglot/init.vim
Line 2350 in bc8a81d
I edit
*.comp
files as GLSL compute shaders, and was rather surprised when they were not highlighted properly due to havingmason
filetype.The workaround is to add
perl
intopolyglot_disable
global variable, asmason
registration happens under "perl is not disabled" condition.But I wonder what is a proper way to fix it.
*.comp
even a valid/common file extension formason
, whatever that is?The text was updated successfully, but these errors were encountered: