If you feel I am "moving the goalposts" why not just prove your original case? If you are spending 5 minutes on reading the source code, why not instead spend them on proving your original assertion is correct? You can…
Honestly, I fail to see the problem, if I had to run `ls --no-awesome-ls-pro-upgrade-msg` once when I installed it the first time. And if I did not like it, I could use one of the alternatives to `ls` or build my own.…
> This is an unreasonable standard when you do not know in advance how big the output is. Why is that unreasonable? Let us say a single job outputs 10% of the free space. As long as you run fewer than 10 jobs in…
> The comparison is not very fair to modern day xargs. I am curious how you come to that conclusion. > `nproc` is a relatively standard utility (coreutils). So, xargs -P$(nproc) gets you core (or core-proportional)…
I think that is the right thing to do: Don't like it? Don't use it. Also: https://git.savannah.gnu.org/cgit/parallel.git/tree/doc/cita...
I still remember when those were not of the "OK, don't show this again" type, so you could not simply stop them first after the first run.
git-bisect is nice if you are looking for a git commit. If you are looking for a limit or the failing part of a file have a look at: https://gitlab.com/ole.tange/tangetools/-/tree/master/find-f...
> Try using GNU parallel to sort a list of numbers, [...] – it's not possible, Yet it clearly is possible, so your blanket statement is clearly wrong. `parsort` a simple wrapper, and this really goes for many uses of…
Your `do_one`: * does not buffer stderr * does not check if the disk is full for a period of time during a task (thus risking incomplete output) * does not clean up, if killed * does not work correctly if…
It is documented in the GNU Parallel documentation: https://www.gnu.org/software/parallel/parallel_alternatives.... If you seriously believe you can implement everything using xargs, then this (contrived) example is for…
If you feel I am "moving the goalposts" why not just prove your original case? If you are spending 5 minutes on reading the source code, why not instead spend them on proving your original assertion is correct? You can…
Honestly, I fail to see the problem, if I had to run `ls --no-awesome-ls-pro-upgrade-msg` once when I installed it the first time. And if I did not like it, I could use one of the alternatives to `ls` or build my own.…
> This is an unreasonable standard when you do not know in advance how big the output is. Why is that unreasonable? Let us say a single job outputs 10% of the free space. As long as you run fewer than 10 jobs in…
> The comparison is not very fair to modern day xargs. I am curious how you come to that conclusion. > `nproc` is a relatively standard utility (coreutils). So, xargs -P$(nproc) gets you core (or core-proportional)…
I think that is the right thing to do: Don't like it? Don't use it. Also: https://git.savannah.gnu.org/cgit/parallel.git/tree/doc/cita...
I still remember when those were not of the "OK, don't show this again" type, so you could not simply stop them first after the first run.
git-bisect is nice if you are looking for a git commit. If you are looking for a limit or the failing part of a file have a look at: https://gitlab.com/ole.tange/tangetools/-/tree/master/find-f...
> Try using GNU parallel to sort a list of numbers, [...] – it's not possible, Yet it clearly is possible, so your blanket statement is clearly wrong. `parsort` a simple wrapper, and this really goes for many uses of…
Your `do_one`: * does not buffer stderr * does not check if the disk is full for a period of time during a task (thus risking incomplete output) * does not clean up, if killed * does not work correctly if…
It is documented in the GNU Parallel documentation: https://www.gnu.org/software/parallel/parallel_alternatives.... If you seriously believe you can implement everything using xargs, then this (contrived) example is for…