libxo
fx
| libxo | fx | |
|---|---|---|
| 17 | 50 | |
| 302 | 18,509 | |
| 2.0% | - | |
| 9.7 | 9.1 | |
| 15 days ago | 6 days ago | |
| C | Go | |
| BSD 2-clause "Simplified" License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
libxo
-
jc: Converts the output of popular command-line tools to JSON
> In FreeBSD, this problem was solved with libxo[0]:
Libxo happens to be in the base system, but it is generally available:
* https://github.com/Juniper/libxo
* https://libxo.readthedocs.io/en/latest/
- Libxo: The Easy Way to Generate Text, XML, JSON, and HTML Output
-
Getting work done with PowerShell on Linux
Or make it flexible:
> libxo - A Library for Generating Text, XML, JSON, and HTML Output
* https://github.com/Juniper/libxo/
* https://wiki.freebsd.org/LibXo
Want structure? Ask for JSON or XML and parse. Otherwise it's the regular text output.
- Libxo: Generate text/XML/JSON structured output in one code path
-
Jc – JSONifies the output of many CLI tools
Can you trust it? Cli tool output is not exactly stable. I thought that's why libxo exists?
https://github.com/Juniper/libxo
- Libxo: Library for Generating Text, XML, JSON, and HTML Output
-
Curl gets a --json flag
Please consider https://github.com/Juniper/libxo or something even better than that.
-
You shouldn't parse the output of ls(1)
That would look a lot like FreeBSD. Many of the FreeBSD userland tools are set up to use the excellent libxo (https://github.com/Juniper/libxo) to allow the user's choice of how things are output.
- The growth of command line options, 1979-Present
- Tips on Adding JSON Output to Your CLI App
fx
- Bash/Zsh autocomplete for JSON fields
- Fx 32.0, now with YAML support too
- Fx JSON viewer now supports YAML
-
Jaq – A jq clone focused on correctness, speed, and simplicity
There's also this awesome tool to make JSON interactively navigable in the terminal:
https://fx.wtf
- Fx 31.0.0 Release
- FLaNK Stack Weekly for 30 Oct 2023
- jq 1.7
-
Modern Linux Tools vs. Unix Classics: Which Would I Choose?
Using awk/sed to parse json seems to be using the wrong tool for the job.
As an alternative to jq with easier to remember syntax, see https://fx.wtf/
Recent discussion: https://news.ycombinator.com/item?id=37567009
- Fx – Terminal JSON Viewer
- fx – terminal JSON viewer
What are some alternatives?
pdfalto - PDF to XML ALTO file converter
jless - jless is a command-line JSON viewer designed for reading, exploring, and searching through JSON data.
elvish - Powerful scripting language & Versatile interactive shell
jiq - jid on jq - interactive JSON query tool using jq expressions
jtbl - CLI tool to convert JSON and JSON Lines to terminal, CSV, HTTP, and markdown tables
jid - json incremental digger
PSReadLine - A bash inspired readline implementation for PowerShell
rq - Record Query - A tool for doing record analysis and transformation
oil - Oils is our upgrade path from bash to a better language and runtime. It's also for Python and JavaScript users who avoid shell!
kubectl-jq - Kubectl plugin that works like "kubectl get" but runs everything through a JQ program you provide
Rustlings - :crab: Small exercises to get you used to reading and writing Rust code!
ngs - Next Generation Shell (NGS)