I suggest adding a tests folder to the project to introduce automated syntax tests. I'm not sure if this feature is supported by Sublime Text 2, but ST3 supports it natively and my guess is that it shouldn't interfere with ST2 users (although I can't vouch for this):
This would allow to run all the test source files against the current Nim syntax with a single Build operation, which is rather practical way to ensure that:
current features are correctly implemented
new changes to the syntax don't break previous behaviour.
If you do add a tests folder somewhere, I'd be happy to contribute some syntax_test_*.nim files.
BTW — wouldn't it be worthy to update the whole package to ST3? From what I read on the ST forum, there are very few ST2 users left today, and the new *.sublime-syntax format is much easier to edit (YAML) and offers better control over the syntax development.
I've worked with the new syntax format and I've found it much more intuitive to work with than the older *.tmLanguage format (even when converting from the *.YAML-tmLanguage intermediate format).
I suggest adding a
testsfolder to the project to introduce automated syntax tests. I'm not sure if this feature is supported by Sublime Text 2, but ST3 supports it natively and my guess is that it shouldn't interfere with ST2 users (although I can't vouch for this):https://www.sublimetext.com/docs/3/syntax.html#testing
This would allow to run all the test source files against the current Nim syntax with a single Build operation, which is rather practical way to ensure that:
If you do add a
testsfolder somewhere, I'd be happy to contribute somesyntax_test_*.nimfiles.