deathaxe
deathaxe
I hesitate approving this change because snippet's content is significantly changed. Changing trigger to reduce duplicates might be ok, but I am not sure whether changed content may cause complains.
I guess all syntaxes should be refactored to use named contexts primarily/only ideally with a common context naming scheme. #3659 intents not to mess with current context naming scheme. In...
Use plural names for non-popping contexts and signgular for popping contexts. Plural makes clear an included context can handle multiple tokens without popping or setting away from current context. (It...
Use primarily (only) named contexts. Reasons: 1. Only named contexts can be extended or overridden by an inheriting syntax definition 2. ST's scope name popup (ctrl+shift+p) displays the name of...
Use variables for large lists of fixed tokens (builtin functions etc.), because 1. they can easily replaced by inheriting syntaxes 2. contexts itself keep readable by avoiding large blocks of...
Not an lua expert, but as `func1` is scoped as dictionary key, I wonder why `func2` is not.
The whole pattern is not scoped as such, nor is the whole `let(...)` statement.
Related with #1358, #2635, #2638.
> Maybe this could be applied to parse RegExp strings and allow consistent syntax highlighting of Regular Expressions in more languages. A very good point. I also wonder why an...
Would be a great improvement (and "some" work to do). Python or PHP already maintain a dedicated own syntax definition file. Perl and some other syntaxes use _Regular Expressions_ syntax....