-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Usage message is misleading when SubcommandsNegateReqs is used #871
Comments
Good catch, I agree. I tend to like the dual line usage, but that may be slightly harder to implement in current clap. I'll play with it and see. |
I noticed that in addition to showing the arg in the help for the main command, it also shows it in the help for the subcommand, but DOES NOT show it if you give a value for it. Really weird. I.e.:
Note how in the last example, the |
…s are used, a new more accurate double line usage string is shown Closes #871
…s are used, a new more accurate double line usage string is shown Closes #871
Affected Version of clap
2.20.5
Expected Behavior Summary
Show a usage message that is more accurate, like
or
With flags it become more difficult to write a usage message...
Actual Behavior Summary
Show a usage message that is misleading
This suggests that a subcommand can be used after
<input>
but it cannot.Steps to Reproduce the issue
The text was updated successfully, but these errors were encountered: