[andreypopp]

checkout http://docopt.org then

[kardos]

That seems to be an abandoned project

[clan]

Yes, according to the archived Rust implmentation[1] which in turn refers you to either clap[2] or structopt[3]. Other implmentations does not mention this but those I looked at had not been touched for years. Either very stable or unmaintained. Unfortunately the latter according to the Rust crate. The dotNet implmentation had a very small version bump in the dependencies but the rest of the project does not seem to have been touched the past 2 years.

[1] https://github.com/docopt/docopt.rs

[2] https://docs.rs/clap/latest/clap/

[3] https://docs.rs/structopt/latest/structopt/

[kardos]

FWIW, there seems to be a less-abandoned fork here: https://github.com/jazzband/docopt-ng

I'm sticking with argparse though

[sandywaffles]

structopt became part of clap proper (as `clap_derive`) when clap v3 was released.

[wingmanjd]

Whoah, that's a neat tool! I definitely need to implement this with my scripts.

Thanks!

[maleldil]

It's abandoned, and tbh it's more trouble than it's worth. It's far easier and more reliable to specify the CLI and have it generate the help text than the other way around. All major languages have good CLI parsing libraries (some in the stdlib itself, like Go and Python).

[kardos]

Yeah..... it seems like it would be fragile and require lots of iterating to converge on a help doc that is both "pretty" and correctly parsed by docopt

[thechao]

It's a neat idea (I maintained an unofficial C port for a while); but, terrible in practice.