binary-parsing VS jq

* binary-parsing - https://github.com/dloss/binary-parsing

There are a few hex/disk editors that support "templates" (but you need most times to create those yourself).

Here is a sort of "curated list" of related tools:

https://github.com/dloss/binary-parsing

The most complete/populated I know of is Kaitai:

http://kaitai.io/

http://formats.kaitai.io/

that you can use with Hiew with Kiewtai

https://github.com/taviso/kiewtai

If the question is slightly different, i.e. which bytes are used to identify a given file format, there is Trid:

https://mark0.net/soft-trid-e.html

Which has also a database of known headers/patterns.

Nice! Some other tools and parsers: https://github.com/dloss/binary-parsing

That should recursively list directories, counting only the files within each, and output² jsonl that can be further mangled within the shell². You could just as easily populate an associative array for further work, or $whatever. Unlike bash, zsh has reasonable behaviour around quoting and whitespace too.

¹ https://zsh.sourceforge.io/Doc/Release/User-Contributions.ht...

² https://github.com/jpmens/jo

³ https://github.com/stedolan/jq

What I miss from jq and what is implemented but unreleased is platform independent line delimiters.

jq on Windows produces \r\n terminated lines which can be annoying when used with Cygwin / MSYS2 / WSL. The '--binary' option to not convert line delimiters is one of those pending improvements.

https://github.com/stedolan/jq/commit/0dab2b18d73e561f511801...

If you have jq installed you can use it to make the output look nicer.

It requires jq for JSON processing and GNU parallel for concurrent searches in the notebooks.

jq is your friend.

The jq command (https://stedolan.github.io/jq/) is useful pulling that information out.