Re:Jo - JSON output from a shell
by networked on Saturday March 12, 2016 @12:26PM
(#11273634)
Neat. An ad hoc alternative to this if you have Python 2.7 handy and can't or don't want to compile C code could be something like
$ python -c 'import json, sys;\
kv = sys.argv[1::];\
v = [int(x) if x.isdigit() else eval(x.title()) if x in ["false", "true"]\
else x for x in kv[1::2]];\
print json.dumps(dict(zip(kv[::2], v)), ensure_ascii=False, indent=2)
' key1 value1 key2 'string value 2' number 5589 boolean1 true boolean2 false
I, for one, am excited to hear that native JSON (and XML, and HTML) output is coming to FreeBSD's userland courtesy of libxo (see https://wiki.freebsd.org/LibXo). I hope GNU Core Utilities eventually go the same way or a full-featured alternative appears for Linux that does.
Re:Jo - JSON output from a shell
by dm3 on Saturday March 12, 2016 @12:20PM
(#11273609)
Very nice. This looks like a great complement to `jt` (https://github.com/micha/json-table) - a tool to turn JSON into plain text tables. Both seem to be super simple tools written in C with no heavy dependencies.
Re:Jo - JSON output from a shell
by techdragon on Saturday March 12, 2016 @10:22AM
(#11273150)
Awesome complimentary program to the `jq` tool.
However... I do wish the name was `json` not `jo`. In my case more for personal reasons regarding painful memories attached to the name 'Jo', but I also think the tool creates JSON, so why not call it `json` or `jp` short for 'json print' ... but the matter appears settled. Oh well.
Re:Jo - JSON output from a shell
by techdragon on Saturday March 12, 2016 @10:50AM
(#11273245)
Yes I can always do this sort of thing. But it would be nice to not 'maintain the illusion' when the future day comes that I've got `jo` installed on my various desktops and laptops, inside containers, on snowflake servers, on cattle servers, used by a growing collection of shell scripts written for various versions of sh and bash, etc...
Re:Jo - JSON output from a shell
by fiatjaf on Saturday March 12, 2016 @11:45AM
(#11273435)
I feel the same.
All these smart small tools are amazing, but they suppose the user has only one computer and does everything on it. so he can just install once and that's it.
I normally use 4 different desktops and 2 VPSs weekly. Although I tend to do most of the work in one of the VPSs, the more I customize it with tools like this, the more all the other computers will miss things.
Re:Jo - JSON output from a shell
by corobo on Wednesday March 16, 2016 @08:59AM
(#11296899)
Late to the party but yes. The idea behind ansible seems to be (I'm new to using it) that you can run the command a million times over a million machines and it'll only install new things to the machines that don't already have it
Re:Jo - JSON output from a shell
by kbd on Saturday March 12, 2016 @11:33AM
(#11273400)
Because the shell substitutes the return code before passing to jo, jo sees 'success@1'. How do you expect jo to know where the 1 came from to change its interpretation?
Edit: or you're saying jo should always consider 0 true and 1 false to match shell return code conventions?
Re:Jo - JSON output from a shell
by kbd on Saturday March 12, 2016 @12:38PM
(#11273670)
> It was merely an observation... jo looked as though it was for use in the shell though, so I was curious as to the design decision here.
I think it makes sense how it is, since if I typed "success@1" I wouldn't expect that to output "{success: false}" but I definitely appreciate your point about a case like "success@$?".
> Of course, one can simply negate the value before passing it to jo.
https://stedolan.github.io/jq/
That's not curl | bash.
That's wget | tar.
However... I do wish the name was `json` not `jo`. In my case more for personal reasons regarding painful memories attached to the name 'Jo', but I also think the tool creates JSON, so why not call it `json` or `jp` short for 'json print' ... but the matter appears settled. Oh well.
All these smart small tools are amazing, but they suppose the user has only one computer and does everything on it. so he can just install once and that's it.
I normally use 4 different desktops and 2 VPSs weekly. Although I tend to do most of the work in one of the VPSs, the more I customize it with tools like this, the more all the other computers will miss things.
What is the solution?
Edit: or you're saying jo should always consider 0 true and 1 false to match shell return code conventions?
It was merely an observation. Of course, one can simply negate the value before passing it to jo.
jo looked as though it was for use in the shell though, so I was curious as to the design decision here.
I think it makes sense how it is, since if I typed "success@1" I wouldn't expect that to output "{success: false}" but I definitely appreciate your point about a case like "success@$?".
> Of course, one can simply negate the value before passing it to jo.
What's the shortest way to do that? This?
Other than that it looks pretty handy.