New features for sublime syntax test v4201+

[jrappen]

Sublime Text Build 4201 and later support new ways to test scope selectors.

Discord: https://discord.gg/D43Pecu

See announcements there.

Compare for details:

https://gist.github.com/BenjaminSchaaf/95567e100e62abb96191b75843ddab39

If you have a license for Sublime Text, you can try out (the currently private) v4201 (or later) by replacing the Build number in the links found at: https://www.sublimetext.com/dev. Updating dev builds will not trigger and update to current dev builds.

FYI @stefanobaghino

[stefanobaghino]

@jrappen Thank you! Catching up with master is proving a lot more challenging than initially thought (I guess I should have known better! 😄), but I would definitely prefer if we could take advantage of the situation to keep up with upstream as much as possible. Personally I don't have an ST license, but I'm sure this will soon become something we need to work on as we bump the sublimeHQ/Packages submodule and this is adopted by grammars.

[jrappen]

It's not yet in master because the syntax test binaries from dev channel aren't updated either. It's only a few "private" betas not yet in the dev channel ... if that makes sense. So Builds 4201, 4202 and 4203 can be used if you have a license (as they are regular dev Builds). The update json channel files for dev still point at 4199, though.

[jrappen]

I sent a message to SublimeHQ on Discord. Maybe they'll help.

https://discord.gg/D43Pecu

[michaelblyons]

This is limited to scope resolution, yes? No tokenization implications?

I suspect (but could be wildly wrong) that color schemes will take a while to make use of them.

Another relevant link: sublimehq/sublime_text#6741

[jrappen]

Limited to scope resolution, yes.

Relevant here though if (default) packages added tests using the new feature and syntect fails those tests because of them. Not sure anybody will touch the color schemes any time soon, would be nice to be wrong.

[jrappen]

4201 through 4204 were only "partially" published.

4205 and the accompanying test binary has now landed in the dev channel, so updating dev Builds should now work as expected as should be using test binaries via GitHub as shown in the default packages repository.