Backtracking on commands about optparse-applicative HOT 4 CLOSED

What's the use case for this behavior? The reason for the current "backtracking" behavior is that it allows "global" options to be specified after command-specific ones.

from optparse-applicative.

My use case is this. I have a tool that can act as a compiler (without subcommands — e.g. tool foo.hs), or as a package manager with the pkg subcommand (e.g. tool pkg dump --user). Now, if the user accidentally misspells an option to tool pkg or otherwise causes the parser to fail, suddenly tool pkg would try to compile pkg, which is unintuitive.

from optparse-applicative.

I see: you have a subcommand which is completely independent from its parent.

It should be easy to selectively disable backtracking. I'll look into it.

from optparse-applicative.

Thank you.

from optparse-applicative.