Ross Patterson

There are some things in `lark.lark` that don't match what `load_grammar.py` implements. For example, I learned the hard way that `load_grammar` only allows rule aliases on top-level alternates, although `lark.lark`...

Sounds good. I wasn't sure which version was definitive. So, basically the loader is correct and the grammar should reflect what it does, right? While I'm at it, I'll take...

PR #1388 submitted for my observations above, plus several others I found.

You're almost certainly processing a UTF-8 document, but not processing it _as_ UTF-8. See https://en.wikipedia.org/wiki/%C3%8F#Computing for an explanation of the mistake.

I needed the same thing, but rather than implement `grep -r`, I did `grep -H`, so `find -exec gron -H` gets you the filename. See https://github.com/RossPatterson/gron (or https://github.com/tomnomnom/gron/pull/72)

@tomnomnom Can you review my pull request https://github.com/tomnomnom/gron/pull/72 for this feature?

It's been several years since I created this PR, but if the gron maintainers are interested in mergong it, I'll make sure the changes are compatible with the current source.

`--no-sort` tells gron not to sort the output. It doesn't guarantee a stable order - if you want that, let it sort. The instability comes from the underlying Go `map`...

The rules in question look like this: ```antlr single_instruction : assignment | keyword_instruction | command_ ; assignment : ( VAR_SYMBOL | SPECIAL_VAR ) EQ expression ; command_ : expression ;...

We should at least compare the trees from each target for every test, and ensure that all targets produce the same tree. We could do that without needing any specific...