jc – JSONifies the output of many CLI tools

Re:jc – JSONifies the output of many CLI tools by berkes on Thursday November 03, 2022 @07:46AM (#33449622)

Is "redundancy" that you have to provide --dig?

I can imagine `jc` having some detection built in, from which it determines the command/content it's being parsed. Doesn't seem to have it, yet, and I'm generally no big fan of "magic" like this, but it would remove the redundancy.

Having it as a pipe, allows for much more, though.

   some_expensive_command > out.log
   jc --expensive-cmd < out.log

   hourly_dig.sh > example_com_records_$(date +%F+%s)
   cat example_com_records_* | jc --dig

[ Parent | on HN ]

Re:jc – JSONifies the output of many CLI tools by kbrazil on Thursday November 03, 2022 @12:07PM (#33453173)

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 syntax.

I did implement auto-detection for `/proc` file parsers so you can just do:

    $ cat /proc/foo | jc --proc

    $ jc /proc/foo

But you can specify each procfile parser directly if you want to as well.

[ Parent | on HN ]