Nikos M.
The parsers created by the grammar addons are similar to [PEGs](https://en.wikipedia.org/wiki/Parsing_expression_grammar) which are mildly stronger than context-free parsers. But there are other features (like grammar `actions`) which **enable strong context-sensitive...
If it can be modelled in a PEG grammar it can be done by the addon. > BNF spec... how deep does that get you? Are you really just lexing...
@yyyc514 My grammar addons have a full-blown PEG-like parser of their own. In fact they all have the same [generic parser](https://github.com/foo123/editor-grammar) and only the interface code changes to adapt to...
@yyyc514 this is exactly what I was doing in the highlightjs-grammar addon, I tried to bypass default hjs tokenizing and replace with the parser of the addon. But (continouing from...
> I'd be curious to know if foo123 just invented this JSON spec from scratch or if it's some type of standard? @joshgoebel The answer is both. As explained [here](https://github.com/foo123/editor-grammar/blob/master/grammar-reference.md#modularity-and-future-directions)...
Adding python implementation is on the wish list. Unfortunately due to other projects and lack of time, I cannot undertake the task at this point, only in some time in...
Update to 1.2.0 (js only) takes some care of this issue, but I am not sure if something else is needed. Take a look. I leave this open.
new upload of v.1.2.0 ``` /\u{61}/u { "type": 1, "val": [ { "type": 32, "val": "u{61}", "flags": { "Char": "a", "Code": "61", "UnicodePoint": true }, "typeName": "UnicodeChar" } ], "flags":...
> /\u{2}/u seems not correctly treated as a unicode char. Fixed ``` /\u{2}/u "\\u{2}" { "type": 1, "val": [ { "type": 32, "val": "u{2}", "flags": { "Char": "\u0002", "Code": "2",...