pkoppstein

@mterron wrote: > I'll make it work :) It appears you are not quite grasping the fact that the implementation of the shell-out function will (of necessity) be designed to...

@mterron - Excellent. You might want to mention your use case on one of the shell-out tracking issues.

Congratulations to @itchyny on gojq's @base64d, which passes the test using https://www.w3.org/2001/06/utf-8-wrong/UTF-8-test.html with flying colors. With B as a local copy of this file: ``` $ base64 < B >...

@GwynethLlewelyn - gojq is unquestionably better than jq in several important respects -- not least that it is being actively maintained -- but unfortunately gojq has one major intrinsic drawback...

@ololoe - Please see the [jq FAQ](https://github.com/stedolan/jq/wiki/FAQ) about hjson and similar utilities. As best I can tell, there is no momentum towards supporting json5 or hjson, but there is perhaps...

See https://github.com/stedolan/jq/issues/1571 regarding jq's support for comments. (The historically minded might also be interested in https://github.com/stedolan/jq/issues/402 .) It seems to me that there have been three main stumbling blocks in...

> How can I make this clearer? How about something like: Here is an overview that summarizes: ☑ features that have been implemented ☐ features that remain to be implemented

@wtlangford- it would really be quite helpful (and easy to implement) if debug/1 defined as follows were always available: def debug(message): (message|debug)as $debug | .; The documentation could give an...

@wtlangford - Please go ahead! Since `debug`'s output is both rigid and often difficult to read, do you think that `debug/2` would be helpful so that (for example) the input...

It's not clear to me whether this is a bug in jq or your program. (*) In any case, `fromstream` expects an "end of object" marker that your filter excludes....