jc – JSONifies the output of many CLI tools

Re:jc – JSONifies the output of many CLI tools by psychoslave on Thursday November 03, 2022 @01:34PM (#33454531)

Following the project documentation, you easily come to:

  jc dig example.com | jq       
  [
    {
      "id": 30081,
      "opcode": "QUERY",
      "status": "NOERROR",
      "flags": [
        "qr",
        "rd",
        "ra"
      ],
      "query_num": 1,
      "answer_num": 1,
      "authority_num": 0,
      "additional_num": 1,
      "opt_pseudosection": {
        "edns": {
          "version": 0,
          "flags": [],
          "udp": 4096
        }
      },
      "question": {
        "name": "example.com.",
        "class": "IN",
        "type": "A"
      },
      "answer": [
        {
          "name": "example.com.",
          "class": "IN",
          "type": "A",
          "ttl": 56151,
          "data": "93.184.216.34"
        }
      ],
      "query_time": 0,
      "server": "192.168.1.254#53(192.168.1.254)",
      "when": "Thu Nov 03 14:06:40 CET 2022",
      "rcvd": 56,
      "when_epoch": 1667480800,
      "when_epoch_utc": null
    }
  ]

Rather readable to my mind. And you can rather easily transform it to your preferred human readable output format I guess.

[ Parent | on HN ]

Re:jc – JSONifies the output of many CLI tools by codedokode on Thursday November 03, 2022 @02:26PM (#33455263)

For me there are too many quotes and brackets. My proposed format can also be converted to JSON if necessary.

[ Parent | on HN ]

Re:jc – JSONifies the output of many CLI tools by kbrazil on Friday November 04, 2022 @12:32PM (#33469458)

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 quite easy to read JSON these days.

[ Parent | on HN ]