Showing global options in command parsers

[chrisdone]

Is it possible to have e.g. foo --help produce

Usage: <interactive> [--version] [--help]  [--verbose ARG] COMMAND

Available options:
  --version                Show version
  --help                   Show this help text
  --verbose ARG            Set verbosity

Available commands:
  dothing                    do the thing

and then foo dothing --help produce

Usage: <interactive> [--verbose ARG] dothing
  do the thing

like that? So that --verbose is still listed because it's a global option but applies to dothing too?

[edsko]

+1 :)

[bollmann]

+1

[HuwCampbell]

I've made some changes to how contexts are carried through, so this should be easier now.

[nomeata]

+1

[nomeata]

I am very interested in having a fix for this. Does anyone maybe have a somewhat doable workaround for this?

[borsboom]

There is a workaround, although it's a bit of work. Basically you have to add the global options parser both in the outer parser and to every subcommand parser, and then you combine the "outer" global options with the "inner" global options (having the inner options take precedence). You also have to make sure you set (prefs noBacktrack) for this case to avoid confusing behaviour. We do this in stack, and the Options.Applicative.Complicated module has most of the guts of that.

[nomeata]

Hmm. Sounds as if its almost easier to only have local options then.

[bitc]

Why was this issue closed? There still doesn't seem to be a way to do this (apart from the complicated workaround of @borsboom)