deathaxe

With regards to https://toml.io/en/v1.0.0#array-of-tables I wonder how strictly we want to follow a "meta.mapping.key" interpretation or how it corresponds/maps to JSON. Current TOML, INI and GitConfig scope sections `[section]` as...

> ... table header should be a single `entity.name.section` (with `punctuation.accessor` on top). Makes sense, but also renders `meta.mapping string` scope for keys somewhat questionalble as those are of exactly...

This may be caused by various `embed`'s being used to support shell highlighting in quoted strings, which are expanded to push...with_prototype, if ShellScript itself is used like this. Well, Makefile,...

> (Is for example `awk -F' c-? '` a long option value, ... Speaking for the shell, yes. Words are separated by space, parens and pipe operators, only. Thus `-f'...

Case patterns actually are pattern lists, rather than a single pattern with alternation. It means each word is a single pattern `pat1 | pat2 | pat3 )`. As such whitespace...

Thank's for your feedback. It turned out to be a long-living design/priority issue, which Bash on master suffers from as well. Fixed.

Great!

I simple fix would probably be to exclude `` scoped `keyword.operator` or `punctuation.accessor`, but maybe a more general solution would be to enable packages to define selectors for opening and...

My current implementation looks like ... Packages/Default/Syntax Tests.sublime-syntax ```yml %YAML 1.2 --- # http://www.sublimetext.com/docs/3/syntax.html name: Sublime Syntax Tests hidden: true scope: text.syntax-tests variables: scope_segment: \w+(?:[\w-]*\+*) # \+* is for the...

Maybe treat it as regular expressions syntaxes, which are assigned to find inputs in _Default_ but are provided via separate _Regular Expressions_ package. Note, the syntax as provided in my...