Johannes Rappen

For Markdown I believe (1) the frontmatter can be JSON and (2) the fenced blocks can be split up into json & jsonc. GitHub flavored Markdown code blocks behaves similar...

> I would suggest to use "invalid.illegal" only if an expression is in an unrecoverable state. Maybe even better to leave such things for linters in general. I think a...

> This still won't work, because of auto-pairing brackets, i.e. you often have one of these characters to the right of the caret while typing. Better remove that rule for...

⚠️ I have addressed and resolved all comments above.

With regards to: - `embed: scope:source.json` - `push: scope:source.json` in Packages **other than** `JSON`, I have: - `LaTeX`: - left as is, because [`minted`](https://ctan.org/pkg/minted) uses [`pygments / JsonLexer`](https://github.com/pygments/pygments/blob/master/pygments/lexers/data.py) - `Markdown`:...

The linked page from above says that extended maintenance for v1.9.3 ended in 2015, so I guess he has a point.

Right. I'm saying both your points are valid.

Just in case you didn't know: - You can ignore [snippets](https://www.sublimetext.com/docs/completions.html#snippets) by using [`ignored_snippets`](https://www.sublimetext.com/docs/completions.html#ignored_snippets): - [Overriding](https://www.sublimetext.com/docs/packages.html#overriding-files-from-a-zipped-package) is also an option.

It would make sense to move these tips into a `./CONTRIBUTING.md` file of this repo to keep them up-to-date with the current release on the `dev` channel.

Most scope naming "issues" are tagged with `RFC` (as is this issue), compare: https://github.com/sublimehq/Packages/labels/RFC