Vladimir Keleshev

Right now in option section any text after an option is interpreted as an argument to that option. Not sure if the best solution would be to raise an error...

@BurntSushi this issue seems like a nice place to write a proposal. No need for PR yet, let's discuss first.

@BurntSushi looks good. Also, I'm pretty sure that future versions of docopt will require you to write `--all=` and disallow `--all ` in usage (but not in command-line). Can't find...

Sorry for late reply. In reference implementation, it is possible to have the following usage: ``` usage: my_program [--my-arg --my-other-arg] [--] [...] ``` In this case, you invocation will capture...

I have not really followed this thread, but I saw a word _dispatch_ mentioned, so I figured I'll paste a link here: https://github.com/keleshev/docopt-dispatch

You need a blank line after the end of your usage-section. From README: > Usage pattern is a substring of doc that starts with usage: (case insensitive) and ends with...

Ok, I think I know what's the problem. Docopt scans for lines that start with `-` when searching for description of options. That is why if one of the lines...

Thanks for noticing this. I will take a deeper look.

Now it is planned that the language-agnostic test-suite (bundled with python implementation) will do the work of ensuring same behavior across implementations. Full grammar is possible, but the language (due...

@RonnyPfannschmidt this was actually more or less done, here is an example of a test-case: ``` python r"""Usage: prog [options] -a All. """ $ prog {"-a": false} $ prog -a...