[quote=“facelessuser”]

Ugh…that will make drop in replacements impossible and require multiple language changes just to drop in a custom JS language. I haven’t upgraded yet to 3087, and probably won’t until some of this is resolved.[/quote]

Well, the most straight forward solution is to just override the original file, which imo is also the most proper way to do this as it allows for consistend syntax def file paths outside of syntax includes (e.g. creating files with a default syntax highlighting using view.set_syntax ).

This can be done currently by creating an override file from another plugin with Python code, but that requires some logic to be properly removable (only remove file on uninstallation, via PC event, if it’s the same as we placed there before) or could be prone to losing modifications if the user happened to have a modified CSS.sublime-syntax file already on his machine.

The other way would be to have a package on Package Control with the same name as a default package (which is currently not allowed due to technical and other reasons!) which can then take advantage of installed packages > shipped packages and still allow users to override. I think I’ve said this a couple times, but I hope that some day we can get proper Package Control integration into Sublime Text, so that all the shipped packages can get updates from publicly accessable and official repositories any time without having to update ST, but this will go a long way. Still, I’m looking forward to that.