-
Notifications
You must be signed in to change notification settings - Fork 56
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
EXIT STATUS section, mention the full command rather than only the sub command. #168
Comments
I disagree, using statuses would convey that it is possible to exit with more than one status. You should read the preamble sentence and each case as a declaration. |
Then perhaps it should be:
|
But then you need to deal with singular and plural. |
Is it likely that it is ever singular however? That seems to be an edge case here. |
Well you won't be the person who gets an issue the day a user of the library falls on the case and decides to report it… |
It has the whole command invocation closes #168.
Regarding 1. I simplified the default |
Thanks! |
It has the whole command invocation closes dbuenzli#168.
Signed-off-by: Etienne Millon <[email protected]>
It has the whole command invocation closes dbuenzli#168. Signed-off-by: Etienne Millon <[email protected]>
When printing the doc for the exit code statuses the following is used:
There are two issues here:
status
should bestatuses
since there is more than one exit code in most cases.should rather be
The text was updated successfully, but these errors were encountered: