3 ms·

Long time ago, a colleague of mine created "evenmoreutils" : https://github.com/rudymatela/evenmoreutils https://github.com/rudymatela/evenmoreutils

efreak 5y ago
Anywait is the tool I've always wanted, and implemented in pretty much the same way I would do so. However, besides waiting on a pid, I occasionally wait on `pidof` instead, to wait on multiple instances of the same process, running under different shells (wait until all build jobs are done, not just the current job). ched also looks quite useful; automatically cleaning the old data after some time is great, as I commonly leave it lying around. age also looks great for processing recent incoming files in a large directory (my downloads, for example) p looks great to me, I rarely need the more advanced features of parallel, and will happily trade them for color coded outputs. I looked to see what nup is because I don't understand the description...only to find out it doesn't actually exist. I'm assuming it's intended to send a signal to a process? But if so, why not just use `kill -s sigstop`? pad also doesn't exist, but seems like printf or column could replace it, as these are what I usually use. I think there's also a way to pad variables in bash/zsh/etc. whl is literally just `while do_stuff; do; done` and repeat is just `while true; do do_stuff; done`. It never even occurred to me to look for a tool to do untl; I usually just use something along the lines of `while ! do_stuff; do c=$((c + 1)); echo $c; done`. While the interval and return codes make it almost worthwhile, they themselves are still very little complexity; parsing the parameters adds more complexity than their implementation does. spongif seems useful, but is really just a variation of the command above.
- prosaole 5y ago
  For color coding try: seq 10 | parallel --lb --ctag ping {}.1.1.1

efreak 5y ago

Anywait is the tool I've always wanted, and implemented in pretty much the same way I would do so. However, besides waiting on a pid, I occasionally wait on `pidof` instead, to wait on multiple instances of the same process, running under different shells (wait until all build jobs are done, not just the current job). ched also looks quite useful; automatically cleaning the old data after some time is great, as I commonly leave it lying around. age also looks great for processing recent incoming files in a large directory (my downloads, for example) p looks great to me, I rarely need the more advanced features of parallel, and will happily trade them for color coded outputs. I looked to see what nup is because I don't understand the description...only to find out it doesn't actually exist. I'm assuming it's intended to send a signal to a process? But if so, why not just use `kill -s sigstop`? pad also doesn't exist, but seems like printf or column could replace it, as these are what I usually use. I think there's also a way to pad variables in bash/zsh/etc. whl is literally just `while do_stuff; do; done` and repeat is just `while true; do do_stuff; done`. It never even occurred to me to look for a tool to do untl; I usually just use something along the lines of `while ! do_stuff; do c=$((c + 1)); echo $c; done`. While the interval and return codes make it almost worthwhile, they themselves are still very little complexity; parsing the parameters adds more complexity than their implementation does. spongif seems useful, but is really just a variation of the command above.

prosaole 5y ago
For color coding try: seq 10 | parallel --lb --ctag ping {}.1.1.1