pueue VS nq

You can probably do a good subset it in bash, it's just a nicer interface with a lot of configurability and several convenience features.

I'm generally a big fan of showing alternatives: https://github.com/Nukesor/pueue/?tab=readme-ov-file#similar...

Would you be willing to write a proper guide on how to do all of these things in bash? It would be great to have this as guide an alternative inside the Pueue wiki and link to it. It'll help people to make a more informed decision on whether they need this tool or not.

there is a command line manager for long running tasks called Pueue. It is released into Nix, Arch, Alpine, Void, etc, but not for Debian based distros. I know that releasing into Debian is a bit more challenging, but I just wanted to ask if anybody here might be interested in packaging it. Just as a disclaimer, I am not the author of this project, just a regular user.

This one? https://github.com/Nukesor/pueue

How about this: https://github.com/Nukesor/pueue/? I have it bookmarked from a thread here from few years back and never got to test it eventually, but maybe it will serve your purposes?

Multiplexing is great for your multiple outputs, but I would highly recommend using pueue & pueued for job control. Lets you organize your background jobs into groups which can be paused, resumed, etc. Also lets you act on jobs from different terminals w/the pueue interface.

pueue -- a queue for tasks, running in background

For the command that takes a long time to complete, I always use pueue to run. This thing let you run multiple commands in order and can schedule the execution later which is really helpful to my workflow.

That said, you're basically building pueue. https://github.com/Nukesor/pueue/blob/main/ARCHITECTURE.md might give you some pointers. From reading it, there seems to be a mishmash of tokio stuff, and then everything gets serialised onto an MPSC channel (that's serviced by TaskHandler, on a single thread that's also responsible for polling for finished processes etc, every 200ms).

exchange for pueue and you can even queue them up.

This is the only one I know of: https://github.com/Nukesor/pueue

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