Repository navigation
README out of date #31
Description
The README makes it seem that --until-error does not require an argument:
Or until it fails with --until-error (which also accepts an optional error code):
But when I try it without an argument, I get this:
error: The argument '--until-error <until_error>' requires a value but none was supplied
USAGE:
loop <input> --count-by <count_by> --every <every> --offset <offset> --until-error <until_error>
So I think that maybe --until-fail is what I want, based on this:
Or, if you have a list of files but need to find the one which causes your program to fail:
$ ls | loop './my_program $ITEM' --until-fail;
But I get this:
error: Found argument '--until-fail' which wasn't expected, or isn't valid in this context
And I still don't know how to run a command until it fails. Seems like it is currently impossible.
Activity
Miserlou commentedon Sep 1, 2018
Yep, that seems like a bug, probably introduced with the refactor. Probably maybe still works with --until-fail 1?
mrcnski commentedon Sep 1, 2018
Ah, nope:
Thanks for replying, cool tool 👍
art-of-dom commentedon Mar 25, 2019
So in the current master, I see
--until-failis works as expected.--until-errorstill has the same message:I'm going to start looking into it unless there are objections.
Miserlou commentedon Mar 25, 2019