Erez Shinan

Oh, I see the problem now. I assumed there was some way to detect it. This sounds like a fundamental problem. Maybe `rich` should implement something like this https://github.com/dalance/termbg

Seems that it doesn't right now. But it never hurts to ask - https://github.com/Textualize/rich/discussions/1170

Lark doesn't have this feature. It was implemented in my previous parsing library: https://github.com/erezsh/plyplus/blob/master/plyplus/plyplus.py#L326 It shouldn't be too hard to port this function into Lark's load_grammar.py

> For now I went with the Earley parser. I'm stuck on the below code. What should it behave like? > > ``` > import lark > > grammar =...

I tested @MegaIng 's example again on the latest master, and looks like this bug is fixed!

I like the idea. I think it's potentially possible to do, using the scan function @MegaIng wrote. I hope one day we'll integrate a stable scan function into Lark, and...

Is there anything I can do to get 1388 merged faster?

I added a few comments.

Yeah, I think we can. Users of

> make Lexer (and therefore Lark) generic over the type to parse I'm not sure what exactly you have in mind, but overall it sounds like a positive thing. Are...