Erez Shinan

It looks like the recipe isn't entirely correct. To get the result, you should call `pi.resume_parse()`. See example here: https://github.com/geographika/mappyfile/blob/master/mappyfile/parser.py#L218 As for the line and column numbers, why don't you...

@kloczek Hello. Exactly which version of lark gets installed? The latest 0.x version is 0.12 (which is 2 years old), and latest lark version is 1.1.7 May I ask what's...

Got it. Can you please test it with Lark 1.1.5 ?

(it's one version before we moved from setup.py to pyproject.toml, which may have caused this problem)

Can you check if this also happens with Lark 1.1.5 ?

@Mazzesy I fixed your url here, but you made the same syntax mistake in the langchain issue. The title comes first, the url comes second.

That's a good point, but I think it's reasonable to say that each rule is surrounded by its own ignore terminals on both sides. And since ignoring something twice is...

I think the main challenge in implementing this would be that in LR parsers it's not clear which rule we are parsing until we reach a reduce. So if the...

Yeah, it's a bit of a confusing situation. For example, this works: ```lark %ignore WS_INLINE %import common (WS_INLINE) DIGIT: "0" | "1" start: a b b a: DIGIT b: /0/...

Yeah, I agree, I don't see a reason why we shouldn't merge them into the same terminal. It might raise some namespacing issues, for anyone relying on the terminal names....