-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
all: return code for invalid options #3331
Comments
I am working on this |
I think we have some incorrect parsing/different output :) many thanks for opening this bug |
I am going through them randomly. I'll create issues for the ones I find at least one of the cause for ERROR. |
Cool, excellent :) |
Small world: |
…U test Closes issue uutils#3331
…U test Closes issue uutils#3331
The discussion here might also be relevant: #3102 (it's the issue that led me to create that issue on clap) |
I think we are good now |
ref: #3320
Edit: Though the below described issue fails the gnu test
tests/misc/usage_vs_getopt.sh
, it does not mark it in ERROR state as I originally thought. I have created another issue #3333 which is causing the test to be marked in ERROR state.This issue will potentially fix the gnu test failure
tests/misc/usage_vs_getopts
. At least, this is one of the issue why the test is in ERROR state.The gnu utils exits with error code 1 when there is a argument mismatch. uutils does not in some (may be all) cases.
gnu
uutils
The text was updated successfully, but these errors were encountered: