The main issue with this is that it doesn’t even get basic features like continuing a aborted queue right,a well designed alternative would be https://github.com/chneukirchen/nq
Keeping the state of queues not only inside the memory, in case your daemon or your OS dies.
nq creates simple files in a directory for each queued command, every time something is done it removes the executable bit from this file.
This allows to reuse queues by chmod +x ,* and then restarting nq.
And it allows multiple queues, each queue has its directory, not just one daemon.
The main issue with this is that it doesn’t even get basic features like continuing a aborted queue right,a well designed alternative would be https://github.com/chneukirchen/nq
What do you mean by
continuing an aborted queue? There is an optionresumeAfterStart, which defaults toFalseto avoid mistakes.Keeping the state of queues not only inside the memory, in case your daemon or your OS dies.
nqcreates simple files in a directory for each queued command, every time something is done it removes the executable bit from this file. This allows to reuse queues bychmod +x ,*and then restarting nq. And it allows multiple queues, each queue has its directory, not just one daemon.