Tips and tricks for using JC interactively, in scripts, and in automation.
In Part 2 we look at using JC to parse URLs, POSIX paths, and git log output.
Tag Archives: jq
JC Tips and Tricks – Part 1
Tips and tricks for using JC interactively, in scripts, and in automation.
In Part 1 we look at using JC as a Subnet Calculator, for exploring X.509 certificates, and for converting dates and timestamps.
Tutorial: Rapid Script Development with Bash, JC, and JQ
Tutorial demonstrating the rapid development of a subnet scanning Bash script made possible with the power of JSON, jc, and jq.
Convert X.509 Certificates to JSON with JC
Learn how to extract X.509 certificate metadata to JSON values for easier use in automation scripts. Works with DER, PEM, PKCS #7, and PKCS #12 files.
Working with JSON in Various Shells
In this article I give a quick snapshot of what it’s like to work with JSON in various traditional and next generation shells. Traditional shells like Bash and Windows Command Prompt (cmd.exe) don’t have built-in JSON support and require 3rd party utilities. Newer shells like NGS, Nushell, Oil, Elvish, Murex, and PowerShell have JSON serialization/deserialization and filtering capabilities built-in for a cleaner experience.
A New Way to Parse Plain Text Tables
A new way to parse ASCII or Unicode plain text tables using jc and jq or jello. No need for grep, sed, or awk!
Practical JSON at the Command Line
Effectively use JSON data at the command line with jc, jq, and Bash. This article provides practical examples of how to improve your scripts with JSON.
JSON Tables in the Terminal
jtbl is simple and elegant. It just takes in piped JSON or JSON Lines data and prints a table. There’s only one option to turn on column truncation vs. wrapping columns if the terminal width is too narrow to display the complete table. It ‘does the right thing’.
Silly Terminal Plotting with jc, jq, and jp
Fun at the command line plotting JSON values at the terminal with jc, jq, and jp.
Bringing the Unix Philosophy to the 21st Century
Do one thing well. For command-line utilities to do their one thing “well” they must include standardized machine-readable output. Linux and all of its supporting GNU and non-GNU utilities should offer JSON output options.