Viewing profile — Nukesor

Fair point, but to be honest, at this point it's just easier to do a: pueue add 'rsync somestuff host:location' And if I notice any problems, I just do a `pueue edit $id` and I'm g…

So, there's a wiki which explains many of the usecases. I specifically didn't want to further bloat the README, as it's already super long as it is.

Interesting. May I ask how many tasks you were managing with Pueue and what your usecase was? I also thought about using alternative formats such as CBOR, but choosing a human-read…

You can probably achieve a good subset of its functionality in bash, it's just a nicer interface with a lot of configurability and several convenience features. I'm generally a big…

Also, editing a command in the middle if you notice a mistake becomes tricky. Pueue also allows you to do stuff like dependencies, which get tricky in bash if a task depends on mor…

Well, if you're planning on running 10 commands sequentially that might take a few hours each, you would have to keep those windows open for quite a while. See https://github.com/N…

Not that I know of. If anyone knows of stuff like that, please let me know, as this is regularly asked for :D. I would be pretty stoked to be hired to build something like that, th…

Yep, that's exactly how it's done :)

Nope. Pueue is designed to handle your usecase times 5+. I'm still using it for your usecase, as I'm already used to the interface by now :D.

This question has been asked quite a lot, so I wrote a FAQ ;D : https://github.com/Nukesor/pueue/wiki/FAQ#why-should-i-use-i...

Hey @abelanger, I got a few feature request for Pueue that were out of the scope as they didn't fit Pueue's vision, but seem to fit hatchet quite well (e.g. complex scheduling func…

Always happy to see my stuff getting recommended :D

I actually wrote a more modern solution to `nq` named Pueue. ( https://github.com/Nukesor/pueue ) There are a lot of examples and a FAQ section + a Wiki, if you're interested in mo…