Tim Radvan

Hi! Sorry to hear you're having trouble; thanks for providing details :-) That's really interesting! I agree your grammar looks normal. I don't have time to debug further right now;...

Can `syntax` export to HTML too? It'd be nice to be able to generate HTML files like the [tosh grammar](http://tosh.tjvr.org/help/grammar/) :)

Really well spotted! Yes, when we overhauled the parser to make it much faster, we never got around to re-inplementing Leo's optimisation (nor to updating the Readme...) I'm very interested...

> some kind of wrapper Pretty much! I propose: * a `nearleyc` wrapper in `./nearleyc.js`, which can be imported via `require('nearley/nearleyc')` * Making sure everything in `lib/` is actually UMD...

I believe the code works as intended, it was originally designed to let you define an object in your JS, like `var ws = {test: ()=>...}`, and then refer to...

No, the code is working as intended.

Yes! One of the nice benefits of an Earley parser is that there’s no pre-compilation step, so you can modify the grammar at runtime. The caveat is that the behaviour...

You've mentioned a couple of problems here: * Partial parses, where the input up to the cursor is valid syntax, just incomplete; * Error recovery, where the parser can "skip...

> The way I did this for Electro Grammar is [to set `keepHistory` to true and roll it back when it fails](https://github.com/monostable/electro-grammar/blob/5ac24f8ebd54236e62dde9d164fcda635f8b63a2/src/parse.js) FWIW, a couple of comments: * For future-proofing,...

> I was going to say we should probably fix the save() documentation but I actually can't find it anywhere Yeah, it's funky new stuff we haven't got round to...