Dev Build 3092 is out now, which resolves the issues in 3091 exposed by some third party packages.
Two other relevant changes:
- All files named ‘HTML.tmLanguage’ are now deprecated and ignored. This is due to all of them being based off of the old HTML.tmLanguage: the correct way to include PHP and Ruby from HTML changed as of 3087. Any packages providing their own must now provide HTML.sublime-syntax instead, or better yet, don’t override the default version at all, and send in a patch. The shipped packages will be published on GitHub once the current series of changes settle down.
- Whenever there is a file Foo.tmLanguage and Foo.sublime-syntax, Foo.tmLanguage will be ignored entirely. This allows packages that provide syntax definitions to provide both tmLanguage and .sublime-syntax variants, for compatibility with older versions of Sublime Text.
3092 may cause issues with SublimeLinter, due to SublimeLinter’s custom HTML.tmLanguage file being ignored now. It seems to work in my basic testing, but it was far from comprehensive.
The sublime-php-grammar package will need to be updated now, to work in the same manner as the shipped PHP package: a top level PHP.sublime-syntax file should include HTML.sublime-syntax, using with_prototype to add support for ‘<?php ... ?>’ syntax.