Support for Lark-style EBNF about language-grammars HOT 3 CLOSED

I'll see what I can do. 👍 Rather than modify EBNF's grammar, though, it'll be better to add a dedicated grammar for LEBNF instead. Lark's format is well-defined and uses a non-conflicting file extension, whereas ebnf.cson attempts to accommodate every syntax variation that might be encountered in .ebnf files (which rarely conform to ISO/IEC 14977).

I have no idea on how to write an atom grammar (I find it poorly documented on atom.io)

It's actually TextMate's grammar format, adopted by Atom/GitHub, VSCode, and Sublime Text. Each have different requirements on file format: Atom uses CSON/JSON, VSCode and TextMate use XML property lists, and Sublime uses YAML. Regardless of their representation, all TextMate-compatible grammars are structurally similar, and the ones you'll encounter are often converted from a TextMate bundle (except mine… I proudly pen them all from scratch).

Other than TextMate's grammar reference, the only other reliable source of info (that I know of) is this blog post. It covers several critical (but undocumented) details of writing a TMCG, and discusses the hacks necessary to work around TextMate's notorious lack of multiline pattern support.

from language-grammars.

Righto, all done! This covers everything in both the docs and Lark's own grammar definition. Here's a preview:

from language-grammars.

I've also submitted a PR to have Lark grammars supported/highlighted on GitHub. See github-linguist/linguist#5049.

from language-grammars.