[quote=“tito”]I’m not sure if I understand these problems correctly, but what I cannot understand is that SublimeLinter needs to replace a complete syntax file to apply minor patches. For this reason I always used github.com/lunixbochs/sublimelint
The diff of these files are very small, I would like to ask if it is possible to add some kind of “patching” feature to .sublime-syntax files? I may be telling non sense, but this of replacing complete files which may already include custom modifications does not look good.[/quote]
I think most custom syntaxes will go away if the syntaxes are open source. The main reason they exist is because the defaults are outdated.
In terms of open sourcing them. The use of custom/alternative snippets and completions is a valid use-case. So dividing the packages into e.g. php-syntax, php-completions, php-snippets, etc allows users to install their own completions or snippets and disable the default ones. If they are not in individual packages you once again see packages hacking things to override defaults. The cost of maintaining a custom syntax is not worth the effort if the default syntax is open sourced, as long as it is maintained, and released regularly with pull requests reviewed and accepted or rejected. The maintenance is mostly reviewing and accepting pull requests. 99% of custom syntaxes will disappear.
The Seti theme defines several syntaxes to fill a void e.g. git, ini, etc. I think Markdown defines it’s own. Those go away with defaults open sourced.
Start with open sourcing one syntax and see how it goes.
