OptionParser: mode for setting up distinct "commands" within a program

[andrewdavidsmith]

I noticed that @egor-dolzhenko implemented this in radmeth and others have done similar things. It's already relatively easy using our OptionParser class, but the facilities for printing help and usage messages are just not there when it comes to the "modes". So this issue involves designing the facilities to print usages messages that indicate what the commands are, and what they do. If a user specifies one of those properly (i.e. as the first argument after the program name), then subsequent requests for help/usage should be "command-specific."

[timydaley]

I think that this is implemented in preseq. Calling preseq gives you
$ ~/preseq/preseq
preseq: a program for analyzing library complexity
Version: 2.0.3

Usage: preseq [OPTIONS]

: c_curve generate complexity curve for a library
lc_extrap predict the yield for future experiments
gc_extrap predict genome coverage low input
sequencing experiments
bound_pop lower bound on population size

And calling each individual module gives you the help commands for that module. Is this what you're looking for?