Skip to content
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

Better error messages for command line problems #28

Open
mooreryan opened this issue May 19, 2016 · 1 comment
Open

Better error messages for command line problems #28

mooreryan opened this issue May 19, 2016 · 1 comment

Comments

@mooreryan
Copy link
Owner

Example is when you pass

-o some_dir -no-check-chimeras

you get

Error: option '-o' specified multiple times.
Try --help for help.

This behavior is correct, but doesn't help the user much. Not sure if I can make a better message or not without fiddling around with Trollop lib though.

@seanmcallister
Copy link
Collaborator

Why don't you just add to the error output something like "Check that long form options are headed by a double dash "--" instead of a single dash, which may lead to this error."?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants