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

Parser does not correctly identify option description if on new line #31

Closed
archshift opened this issue Oct 30, 2015 · 3 comments
Closed

Comments

@archshift
Copy link

Example of what does not work:

Options:
  --path=<path>
            Some description of what is happening with this path

Error:

Docopt usage string could not be parsed
--path must not have an argument

Examples of what does work:

Options:
  --path=<path> 
            Some description of what is happening with this path
  --path=<path> [default: somedefault]
            Some description of what is happening with this path
  --path=<path>  Some description of what is happening with this path

(for the first working example, note the extra space after --path=<path>

System:

OS X El Capitan (10.11)

@jaredgrubb
Copy link
Member

This sounds like the patch being requested in #22. Does that seem to match what you are asking?

@archshift
Copy link
Author

Yes, it would seem so.

@jaredgrubb
Copy link
Member

I'm going to close this as a dup. Please let me know if you disagree.

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