Tyler Temp

@joserprieto Thx. It works on Ubuntu 15.05 :+1: :)

Could anyone knows how to fix this folk & fix this dependence problem? (Because of [#4](https://github.com/zhangshine/MdCharm/issues/4))

:+1: How I wish I cloud see this PR earlier

Hey all: I wrote a project called [docpie](https://github.com/TylerTemp/docpie/), which is similar to `docopt` but with the feature above (and also some other features & differences): ``` python """Usage: prog [options]...

Hi, What about to PR to [docopt-ng](https://github.com/bazaar-projects/docopt-ng) which looks like more activately maintained?

@Odyseus is currect and the reason is: `docopt` recognize any line starts with `-` as option section, so ``` --job_dir --checkpoints_dir --log_dir [--period ] [--load-checkpoint ] ``` and ``` --job_dir...

try: ``` Usage: $0 encrypt [options] -w -o $0 decrypt [options] -w -o Options: -w note: in docopt option flag can only accept zero or one argument(s) -o ```

Forked & maintaining: [docopt-ng](https://github.com/bazaar-projects/docopt-ng) Similar implementation: [docpie](https://github.com/TylerTemp/docpie) And yeah I agree that `docopt` need to update its status, as there are indeed bugs exist.

No. This is not supported by `docopt` because of the `docopt` parse tree. Also this is not standrad POSIX cli, because an option flag should only accept none or one...

If you mean: when user gives non-match cli args, print usage and options I guess the answer is: no api in docopt can do this, according to [source code here](https://github.com/docopt/docopt/blob/master/docopt.py#L22-L29)...