binary-parsing VS nq

* 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

If you want something quick and janky, I suggest nq. It's stupidly simple and lightweight; it just requires that everyone is running as the same user. And only lets exactly one job of any kind run in a given queue. There's basically zero configuration; just nq , and it'll either start running , or will wait its turn.

For your ad-hoc uses, I would introduce nq. It's an extremely lightweight queuing system, which gives you two things with minimal overhead:

I'm already aware of alternatives which I will consider (at, nq, snooze, but I still want an accurate lightweight CLI stopwatch/timer app and the script otherwise works well--this is more of an exercise on understanding background processes and could be handy in other scripts. Or if the attempt is considdered hacky and ill-advised, I'm curious of an alternative implementation. I just feel nothing is more simple than a very lightweight C-based timer app that exits 0 after specified time has elapsed and don't want to run a cron job or even a while sleep 1 loop for a reminder (sleep isn't even a builtin...).

Interesting project. Unfortunate that its name conflicts with one of nq’s executables (https://github.com/leahneukirchen/nq), but I’m not sure anything can be done about it.

nq