-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
README out of date #31
Comments
Yep, that seems like a bug, probably introduced with the refactor. Probably maybe still works with --until-fail 1? |
Ah, nope:
Thanks for replying, cool tool 👍 |
So in the current master, I see
I'm going to start looking into it unless there are objections. |
Sounds good! I think it should error out for any non zero, unless they
supply an error code, in which case only exit on that
…On Sun, Mar 24, 2019 at 9:32 PM art-of-dom ***@***.***> wrote:
So in the current master, I see --until-fail is works as expected.
--until-error still has the same message:
error: The argument '--until-error <until_error>' requires a value but none was supplied
I'm going to start looking into it unless there are objections.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#31 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAIi04hbcuIzL0cuypSDirto9yv5lAhBks5vaCcfgaJpZM4WTKB2>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The README makes it seem that
--until-error
does not require an argument:But when I try it without an argument, I get this:
So I think that maybe
--until-fail
is what I want, based on this:But I get this:
And I still don't know how to run a command until it fails. Seems like it is currently impossible.
The text was updated successfully, but these errors were encountered: