Thank you for your very helpful extension! I'm the author of a Visual Studio extension for GLSL language services.
I register file extensions targeted by my extension via IFileExtensionRegistryService.AddFileExtension on package startup because users can choose custom file extensions with an option page.
If I install your TextmateBundleInstaller together with my extension, extensions registered by both extensions (namely .frag and .vert) are handled by your extension. From your readme I assumed that more specialized extensions, like my own, would remain in control of registered file extensions.
I'm happy to fix my extension if you can suggest a way how I can prioritize my registered file extensions over ones registered via a Textmate bundle.
Installed product versions
Description
Thank you for your very helpful extension! I'm the author of a Visual Studio extension for GLSL language services. I register file extensions targeted by my extension via
IFileExtensionRegistryService.AddFileExtension
on package startup because users can choose custom file extensions with an option page. If I install your TextmateBundleInstaller together with my extension, extensions registered by both extensions (namely .frag and .vert) are handled by your extension. From your readme I assumed that more specialized extensions, like my own, would remain in control of registered file extensions.I'm happy to fix my extension if you can suggest a way how I can prioritize my registered file extensions over ones registered via a Textmate bundle.
Steps to recreate
simple.vert
with contentvoid main() { gl_Position = vec4(1.0); }
Current behavior
No error tagging and highlighting of GLSL key words, like
gl_Position
in .vert and .frag files.Expected behavior
The SyntaxHighlightingPack should give priority to a VSX that registers file extensions via
IFileExtensionRegistryService.AddFileExtension
.