Woohoo!!! First issue!! 🎉 😁

I'm in the process of preparing for Linguist 7.6.0 and I've just updated all the grammars and this repo, used by several grammars in Linguist, has been flagged by the grammar compiler:

• repository vendor/grammars/ABNF.tmbundle (from https://github.com/sanssecours/ABNF.tmbundle) (1 errors)

  • Duplicate scope in repository: scope source.abnf was already defined in repository vendor/grammars/language-grammars (from https://github.com/Alhadis/language-grammars)

• repository vendor/grammars/EBNF.tmbundle (from https://github.com/sanssecours/EBNF.tmbundle) (1 errors)

  • Duplicate scope in repository: scope source.ebnf was already defined in repository vendor/grammars/language-grammars (from https://github.com/Alhadis/language-grammars)

• repository vendor/grammars/language-grammars (from https://github.com/Alhadis/language-grammars) (1 errors)

  • Missing include in grammar: source.lex.regexp (in grammars/lex-regexp.cson) attempts to include escapes but the scope cannot be found

The easy solution is to not bump the SHA for this submodule, but the two grammars at the top may be better than what we're already using in Linguist so maybe a few switcheroo PRs are needed for Linguist?

LBNF would be nice so my https://bnfc.digitalgrammars.com/ grammars could be highlighted 😄

How do I specify a production rule allowing a literal DQUOTE?

For example, check out RFC 2045. They appear to use prose-val to specify a literal double quote <">, but it would seem that char-val otherwise allows """. Both options cause a "run-on" quoted string in the syntax highlighting (see screenshot).

The formal ABNF specification specifies:

char-val       =  DQUOTE *(%x20-21 / %x23-7E) DQUOTE
prose-val      =  "<" *(%x20-3D / %x3F-7E) ">"

Also, thanks a lot for making this!

Lark is a parsing library for python. It's flavored EBNF files (.lark) needs syntax highlighting. The only difference between lark EBNF (which I'll refer to as LEBNF) and EBNF is that LEBNF's comments are js-style, without multi-line comment support, brackets denote optional groups, a ? and/or ! are operators that may appear before the definition of a rule or TERMINAL, priority, denoted by TERMINAL.number, is a thing, and it has %import, %ignore, and %declare statements.

Detailed grammar reference can be found here

Would you modify EBNF.cson, and turn it to LEBNF.cson, please? I have no idea on how to write an atom grammar (I find it poorly documented on atom.io)

👋 I'm in the process of updating the grammars for v7.15.0 and noticed the source.ebnf grammar now has invalid regexes:

- [ ] repository `vendor/grammars/language-grammars` (from https://github.com/Alhadis/language-grammars) (2 errors)
    - [ ] Invalid regex in grammar: `source.ebnf` (in `grammars/ebnf.cson`) contains a malformed regex (regex "`"(?!")|(?=^\s+*\S+?\s+::{0,2}=\s`...": nothing to repeat (at offset 14))
    - [ ] Invalid regex in grammar: `source.ebnf` (in `grammars/ebnf.cson`) contains a malformed regex (regex "`'(?!')|(?=^\s+*\S+?\s+::{0,2}=\s`...": nothing to repeat (at offset 14))