-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
process.exit(64) #435
Comments
I'll also fix #188 at the same time. |
@hildjj Hi, But I don't think in the current form this fixes #188. It wants an optional exit code for help, mainly because of something went wrong and we are gracefully exiting strategy. Something like this: function addUser (userName, options) {
if (!Users.hasUser(userName)) {
errorOutput('unknown user:', userName);
program.help(1); // wrong parameters, print help and exit
}
// do something awesome
} Of course with your modification you can do this by executing It would be nice (but not necessity) to combine these statements. If you invite me to your reposity I'm happy to collaborate. |
Referenced from #945 This issue has not had any activity in over six months. It isn't likely to get acted on due to this report. Feel free to open a new issue if it comes up again, with new information and renewed interest. Thank you for your contributions. |
When you call exit, the return code probably should not be
0
(success). Traditionally, option parsing errors have resulted in error code 64, as documented in many systems'sysexits.h
header file, which on my system says:I would be happy to submit a PR if you're open to this change.
The text was updated successfully, but these errors were encountered: