deathaxe
deathaxe
TBH, I am a bit uncertain about it. While being fine with scoping source code `source`, arguments about backward compatibility with existing maybe no longer maintained color schemes is to...
This is true but absolutely unrelated. Both represent structured key-value pairs. YAML is even a super-set of JSON. As such, both now use the same scopes for `keys` and `values`....
Do we really want to bind `*.ins` file extension to that syntax? Probably high risk of false positives, no?
Updates requests for default color schemes are still pending (https://github.com/sublimehq/sublime_text/issues/3590).
That's a known limitation as it is not yet very clear how to reliably distinguish constants and types in normal expressions.
There are several situations Github's and all those other TextMate syntaxes' highlighting fails, too, especially if expressions like types use several lines. Haskell just doesn't provide enough boundaries to pop...
If it is so easy - hey - it's an open source project. Everyone can contribute valuable improvements.
bash is not fully forward compatible with zsh. Fully supporting ZSH requires a dedicated ZSH.sublime-syntax be added. There are even maybe more shell dialects needing special treatment (see: #2638).
Bash already does so every here and than. They shouldn't have negative effects on Bash syntax itself though, which is not always possible. Hence #1358 is still open.
It turned out not to be a ZSH related issue, but more a general problem of priorizing braces in expansions. It effects Bash as well.