Michael Färber

Perhaps to further motivate the proposed change: The current behaviour of jq is not documented AFAIK, and documenting it would probably confuse users quite a bit. In particular, the current...

@pkoppstein, thanks again for your input, especially your quote from the jq language description: > Data symbol bindings are introduced with expr as $NAME | .... The | is required....

Hi @pjungkamp, thank you for your comment! In principle, I am sympathetic to creating a man page for jaq. The question is: What should really go into it? To answer...

> I love the `awk` man page. But I think adding the language grammar to the man page of `jaq` isn't necessary. And I think that `jaq`'s manpage would be...

> I'd like to see: These points look very reasonable to me. If I understand you correctly, you would like a short reference. > I think the `jq` man page...

(By the way, this motivated me to support URLs such as in the jaq playground, in case we want to generate an HTML version of the jaq manual and create...

> "bla" as in bla bla bla? 😬🤔 "bla" as in "Better Label Arriving". ;) I'm not sure yet what exactly should go into this new crate. At the beginning,...

Hi @xorhex! [jaq 3.0 (alpha)](https://github.com/01mf02/jaq/releases/tag/v3.0.0-alpha) should have what you need --- see `jaq_json`'s `sync` feature. By the way, if you want better file loading performance, then I recommend loading JSON...

If you just want to process multiple files in parallel, you could also just use something like [GNU Parallel](https://www.gnu.org/software/parallel).

I agree with you. Would you like to contribute by expanding the example code / documentation in a way that you see fit?