pkoppstein

Thanks. Might I suggest --jq ...; it is customary to use -jq as a contraction of -j -q

I am not advocating the compression of short options. Anyway, I think your point about "-jq" confirms the wisdom of not using "-jq X" to mean "--jq X". That is,...

@ruby0x1 - No, this question has nothing to do with wren-console or JSON. It is about specifying the location of a module in an arbitrary location, as per the "subject"....

@joshgoebel - I've added ER to the "subject" as you suggested. I was originally going to do so, but then I came across the munificent quotation at the very top...

@nicowilliams wrote: > I care about limiting complexity here From what I've been able to glean from the back and forth here, it would seem the module system has drifted...

@nicowilliams wrote: > You can `import "Shazam" as Shazam;` Yes, but from what I understood of the back-and-forth, the proposal is that if Shazam.jq is in ~/.jq/Shazam/Shazam.jq (as we agreed...

@nicowilliams wrote: > No, you won't be forced to do that. Excellent! > If you propose a decent syntax for it other than `import "...";` then I'll restore it. I...

@joelpurra wrote: > I start with a dot in my path, ./.jq/packages/, meaning package-relative paths. Did you mean "project-relative paths"? In any case, regarding not having to type `-P `,...

@jelpurra wrote: > I foresee a lot of confusion. What if packages start to expect to be imported into the "current namespace"? I assume you meant to write "a module"...

@nicowilliams wrote: > What would such a file have? I have probably missed something in the cross-fire, but isn't the issue under consideration how to determine which .jq/ **directory** to...