Jon Sequeira

Can this behavior be accomplished using `Command.AddGlobalOption` on the command whose child commands you'd like to share options with?

With either arguments or options you can also add them to multiple positions within the tree: ```cs var inputArg = new Argument("input"); var cmd = new RootCommand { new Argument("serviceUrl"),...

To specify that the child commands require this argument, while also allowing it in the position immediately following the root command / arg0, you can do this: 

Agreed. I think there are two different concerns here that are unfortunately coupled. * The parser configuration. (Is the one I've suggested behaviorally correct?) * The help output. (Clearly not...

> What's especially misleading is that, while outerCommand --help would print > `outerCommand innerCommand` This help is quite misleading. We should fix it as part of [this issue](https://github.com/dotnet/command-line-api/issues/1334#issuecomment-1171633836).

I wasn't able to reproduce this. Could you provide a more detailed repro? Here's what I tried:

Our focus for validators was to validate parsing more than application logic. (I know this can be a blurry distinction and I'm not suggesting you're using it the wrong way.)...

Does this test case help illustrate the usage? https://github.com/dotnet/command-line-api/blob/5618b2d243ccdeb5c7e50a298b33b13036b4351b/src/System.CommandLine.Hosting.Tests/HostingHandlerTest.cs#L57-L86

This was by design (#1665) and an attempt to bring the behavior more in line with some of the more common response file parsing behaviors, but there's unfortunately little consistency...

Here's an example showing how to restore the old response file parsing behavior, so that each line is treated as a single token and doesn't need to be wrapped in...