-
-
Notifications
You must be signed in to change notification settings - Fork 648
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
Return a non-zero exit code when a command fails because of an issue with the scripting addition #181
Labels
suggestion
Request for new feature or some form of enhancement
Comments
koekeishiya
added
the
suggestion
Request for new feature or some form of enhancement
label
Sep 3, 2019
Do you think it is useful as an end-user to be able to tell the difference between the various ways the scripting-addition fails, or is a generic catch-all "the operation could not complete due to an error with the scripting addition" good enough (with a non-zero exit code of course). |
If I recall correctly I wanted to write this in some place:
So just failing with a generic code is enough. |
koekeishiya
added a commit
that referenced
this issue
Nov 15, 2020
… non-zero exit code upon failure
koekeishiya
added
the
addressed on master; not released
Fixed upstream, but not yet released
label
Nov 15, 2020
koekeishiya
removed
the
addressed on master; not released
Fixed upstream, but not yet released
label
Dec 3, 2020
unrevre
pushed a commit
to unrevre/yabai
that referenced
this issue
Jan 26, 2022
…ails because of the scripting addition
unrevre
pushed a commit
to unrevre/yabai
that referenced
this issue
Jan 26, 2022
…d return a non-zero exit code upon failure
unrevre
pushed a commit
to unrevre/yabai
that referenced
this issue
Jan 26, 2022
…ld return a non-zero exit code upon failure
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Feature request
Return a non-zero exit code if a command fails because the scripting addition is not installed or failed to get addresses.
This would be nice for scripts so chaining with
&&
orset -e
fails early. Currently there's no error message printed to stderr and the exit code is 0, indicating success.The text was updated successfully, but these errors were encountered: