MegaIng

@erezsh That leads exactly to the problem @ornariece describes, since imports (and then includes) are added before anything in the grammar is done, meaning that an included grammar could not...

> I think that's the desirable behavior. I disagree. Including a grammar should behave no different then just pasting the entire content at that place.

@erezsh That is the plan, but that is interdependent of this PR. I will create one for those changes.

Well, `match_examples` succeeds (e.g. not fails), but does not produce the correct result.

A workaround that is not quite good, but at least doesn't crash is to use `use_accepts=False`, but I am looking into a fix.

Ok, this is major: When you have that kind of Transformer, the exception can't even be displayed correctly, it only shows ``.

Does this branch work: https://github.com/MegaIng/lark/tree/fix-accepts If it works, this was surprisingly little effort.

I don't think setting the option automatically when using `parse_interactive` is required, it can just be in all examples and mentioned in that functions documentation that it's suggested to have...

This is probably better as a single Terminal (e.g. everything UPPERCASE). (Or at least a few sections as Terminals). Also, this should be added to the example which compiles all...

This is a drawback of the `earley` parse at the moment. If you use `lalr` instead (which you grammar should be fine for), you already get nicer messages. You can...