deathaxe

Agree. The backward compatibility concerns are mainly tarteting the syntax's main scope here. If a derived/extending syntax adds more patterns, it's ok to only add it's trailing part of a...

JSON with Comments (jsonc) is just an extension of JSON. I don't therefore see any value in adding a _JSON (Basic)_ which _JSON_ is derived from by just adding some...

> I'm still undecided if I should add more flavors in this step ... or do that later. This was just some preparation for (possibly) later. Haven't investigated any other...

You are right @michaelblyons. Nothing is included then. So it's not an option.

He suggests not to highlight incomplete numbers illegal, but keep trailing punctuation unscoped instead. I fully support his arguments. Syntax definitions should handle incomplete expressions/statements/tokens gracefully as it is probably...

If it is invalid, just don't type it this way. Highlighting is just lazy with what's allowed / prebended in front of SH.

The path may posssibly to point to anything there are propably too many variants to catch them all. Improvement suggestions are always welcome at https://github.com/sublimehq/Packages/pulls though.

How about just not using that snippet? Removed things tend to cause someone to complain for whatever reason. Just imagine maintainer of old code bases maybe relying on older ruby...

I have [this Erlang conversation](https://github.com/sublimehq/Packages/issues/2401) in mind when it comes to supporting legacy stuff. So if we don't remove keywords from a language, which have been deprecated since 2007, why...

> How about adding `clab` for the trigger? Looks like a reasonable change / trigger.