pkoppstein

@nicowilliams - Your idea of 'def $name' fits in nicely with the existing '--arg/--argfile/--argjson' framework, and I suppose that means compile-time evaluation, though I did have lazy (on-first-invocation) evaluation in...

> What should happen in a case like def $foo: range(5); An even worse case is `def $foo: empty;` since in that case there is no first item in the...

@nicowilliams wrote: > If it's a constant value, then the name should be $whatever. I'm fine with that, but since (as you say) "functions take inputs, so we'd have to...

> I think that's fine. Yep. Thanks!

@nicowilliams wrote: > I fixed one of @pkoppstein's module issues Thank you for restoring the ability to import into the caller's namespace. That's great, but since you seem to have...

> How about `include "stuff";` for importing into the namespace and `import "stuff";` for importing with the module's basename as the prefix? Having one's cake and eating it too? Beautiful!

``` $ jq -n -r 'include "Abracadabra"; hi' Thank you! Sincerely, ~/.jq/Abracadabra/Abracadabra.jq ```

underscore (https://github.com/ddopson/underscore-cli) has a parameter that influences the degree of compactness, e.g. ``` $ underscore --wrapwidth 100 pretty < input.json { context: [ { name: "John", node: [{ id: 1,...

@kklingenberg - Good catch re `jaq -n '"{}"|tonumber'`. That's a bug that needs fixing. Since different dialects of jq have and will probably continue to have very different implementations of...