Josh Goebel

@RunDevelopment How would you feel about some sort of cross-posting of this?

> I tried to reproduce the issue using your jsfiddle, but the typescript generic is not even displaying there ¯\(ツ)/¯. Because you haven't properly escaped `` in your HTML, etc.

Not sure I follow this `

#3604 might be a reasonable fix. Thoughts?

Did you glance at the PR? See the description for the strategy we're using.

As you see from the other issue it seems like if we add the `=` case that I think now we're covering all the bases?

Considering pulling sublanguage *fully* private as well and we'd allow for `language:xml` scopes instead which would trigger the HTML output's special `class='language-xml'` rendering behavior... so it would be just another...

> addSublanguage and addKeyword can be sort-of merged into openNode? Well, built on top of, yes... I'd move the functions back into the core library and out of the emitter...

@foo123 > The answer is both. As explained [here](https://github.com/foo123/editor-grammar/blob/master/grammar-reference.md#modularity-and-future-directions) the format used BNF+JSON, combines two standards: BNF format for grammar specification and JSON format (that includes the BNF format) as...

> as long as there are ways to bypass the default tokenizer and there is a way to provide the actual token That's what #3620 allows. It should land in...