Skip to content

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

Closed

Description

@archshift

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)

Activity

  1. jaredgrubb commented on Nov 2, 2015

    @jaredgrubb
    Member

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

  2. archshift commented on Nov 2, 2015

    @archshift
    Author

    Yes, it would seem so.

  3. jaredgrubb commented on Nov 14, 2016

    @jaredgrubb
    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

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions