pkoppstein

Assuming we’re ok with the license, I’d suggest NOT making its inclusion conditional, partly because the functionality that will be enabled is so central to Unicode and thus JSON, and...

> asking for us to make sure all non-static symbols are named jq_... or _jq_... or jv_.... Couldn't we just add `utf8proc_` to the list of "reserved prefixes"? See https://juliastrings.github.io/utf8proc/doc/utf8proc_8h.html...

@liquidaty - I'm not sure what exactly is holding up merging this PR, but I noticed: "This branch has conflicts that must be resolved".

@liquidaty - I couldn't find any entries for the new filters in manual.yml. Also, would it help the review process if the commits were "squashed"?

@liquidaty - Hopefully someone more knowledgeable than I am will chime in to answer your questions. In this case, I think "squashing" would be helpful; if you think there's too...

@itchyny wrote: > I would argue that unicode_ prefix would help users understand the difference against ascii_*. As the person who (implicitly) suggested not using a prefix, let me explain...

@itchyny wrote: > upcase | downcase isn't an identity operation for their alphabet [Turkish] Consider also the case of `mu` and `micron`: ``` ./jq -ncM '"µ" | ( . ==...

Please note that, for better or worse, jq behaves just like `cat`: ``` $ cat foo.txt bar.txt foo1 foo2bar1 bar2 ``` In other words, stringing together file names on the...

Being able to fetch a URL programmatically would be very handy. To quote @nicowilliams with regard to some work in that direction: > Hey, this is very cool! Thanks! I'll...

@G-Rath - Apparently not anytime soon. So, besides redirecting /dev/null (or NUL:), you may also wish to consider using `halt_error/1`, e.g. jq -n '{a:1} | if has("a") then null|halt_error(1) else...