Viewing profile — kbrazil

There could be a major schema change that breaks the contract, but one of the nice things about JSON output is that it allows the creation of new fields without affecting downstrea…

`jc` supports plugins: https://github.com/kellyjonbrazil/jc#parser-plugins

`jc` author here. I've been maintaining `jc` for nearly four years now. Most of the maintenance is choosing which new parsers to include. Old parsers don't seem to have too many pr…

Also, `jc` automatically selects the correct /proc/file parser so you can just do `jc /proc/meminfo` or `cat /proc/meminfo | jc --proc` without specifying the actual proc parser (t…

You can do it like this with Jello (I am the author): jello '[e.commit for e in _ if e.commit.author == "Tom Hudson"]' Jello let’s you use python syntax with dot notation without t…

Interesting - the proc-pid-parser actually parses that file name just fine: $ echo '2001 (bad) S 1 2 3 4 5) S 1888 2001 1888 34816 2001 4202496 428 0 0 0 0 0 0 0 20 0 1 0 75513 115…

It doesn't look like jc suffers from this bug since the regex match is greedy: % echo '2001 (my (file) with) S 1888 2001 1888 34816 2001 4202496 428 0 0 0 0 0 0 0 20 0 1 0 75513 11…

jc[0] supports proc files. Converts them to JSON or YAML. (I am the author) [0] https://kellyjonbrazil.github.io/jc/docs/parsers/proc

Fortunately `jc`[0] does parse `/proc/ /stat` correctly. I, of course, originally implemented it the naive/incorrect way until a contributor fixed it. :) $ cat /proc/2001/stat | jc…

Both ways work: $ jc ifconfig lo0 $ ifconfig lo0 | jc --ifconfig

Good news - `jc` supports JSONLines output for many commands and file-types, too!

Also note that you are looking at plaintext output here. By default `jc` and other JSON filtering tools do syntax highlighting when outputting to the terminal so it's actually quit…

Hi - jc author here. Just a couple points: The casting to int/float is not done unless the underlying values are predictably documented to be numbers. There are rare cases where au…

Feel free to open issues on GitHub if you would like to recommend parsers! Also, the latest version of jc supports parsing of /proc files, which may also help.

Hi there! `jc` author here. Yes, it is a documented caveat[0] that the `C` or `en_US.UTF-8` locales should be used for best results. It's not unheard of for tools to require `C` lo…

You can also run `jc -h --dig` to get the parser details that include the schema. Having true JSON Schema[0] is being considered, but on the back-burner due to the sheer number of …

`jc` is available today as a compiled binary with all dependencies self-contained. The binaries and OS package installers are available under the GitHub Releases: https://github.co…

Hi there - author of `jc` here. I originally intended to have auto-detection but put that on the backburner to focus on creating parsers, especially after introducing the magic syn…

Hi there - `jc` author here. `jc` can also output in YAML format with the `-y` flag. It is fairly trivial to add other options in the future since `jc` just turns the text into obj…

Hi there - I'm the author of `jc`. I also created `jello`[0], which works just like `jq` but uses python syntax. I find `jq` is great for many things but sometimes more complex ope…

Similar in concept to jello[0] which works like jq but uses python syntax. [0] https://github.com/kellyjonbrazil/jello

You could do something like this in pure python without the json loading boilerplate with jello[0]. An interactive TUI for jello called jellex[1} is also available. (I am the autho…

For those who are comfortable with python, I created Jello[0], which works like jq but uses python syntax. I also created Jellex[1], which is a TUI built on Jello to assist with bu…

What I was getting at is: cpu: 0.2 kw_read_s: 0.12 is describing a single 'object'. How do you describe an array or list of these objects? Something like: cpu: 0.2 kw_read_s: 0.12 …

New parser contributions for JC are always welcome!