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
After downloading this plugin from package control, no AWK entry was available in the syntax dropdown for me. Looking through the commit history a bit, 9422856, where .YAML-tmLanguage was converted to .sublime-syntax, piqued my interest. Sure enough, reverting to the parent commit 7ec7d15 makes it work for me in ST2. It seems like .sublime-syntax only works in ST3.
Was support for Sublime Text 2 dropped intentionally?
The text was updated successfully, but these errors were encountered:
I fear back porting the changes done in sublime-syntax to handle regex / division ambiguity could be a challenge also as its a different parsing model. So not something I plan to do.
If it's possible to keep an older syntax definition for ST2 while still using the new sublime-syntax for ST3 I guess a pull request to that effect would do.
After downloading this plugin from package control, no AWK entry was available in the syntax dropdown for me. Looking through the commit history a bit, 9422856, where
.YAML-tmLanguage
was converted to.sublime-syntax
, piqued my interest. Sure enough, reverting to the parent commit 7ec7d15 makes it work for me in ST2. It seems like.sublime-syntax
only works in ST3.Was support for Sublime Text 2 dropped intentionally?
The text was updated successfully, but these errors were encountered: