Jon Sequeira

I understood that `AddGlobalOption` gives the desired behavior. The way this works is that it effectively adds the specified option as a child of the `Command` you invoke it on...

@franklupo What you're seeing is because your required options were only added to the root command. This means they're only required when invoking the root command. If you add them...

If the option is global then it can be specified in either position. Either of these would be valid: ```console > myapp --port 123 > myapp send --port 123 ```

I notice that you're using a number of non-generic `Option` instances. This class has been made `abstract`. Try changing `new Option` to `new Option` for the name and email options...

I'm still not clear what the issue is. What are you seeing and what are you expecting to see? If you're expecting to see an error on `send verify` because...

Currently you've only added it to the `send` command so it is only required when the `send` command is the one being invoked. But once you specify `verify`, then `send`...

> If anything, then the solution to this issue is to document AddGlobalOption(). @ptr727, the documentation for this feature can now be found here: https://docs.microsoft.com/en-us/dotnet/standard/commandline/define-commands#global-options

> If mandatory it should ask. @franklupo A required option is only required when it's in scope. Take this example: ```csharp var root = new RootCommand("myapp") { new Command("one"), new...

I think this is great. I'd like to throw out some related ideas and get people's thoughts. Our discussion around `#r "project:` (spanning both F# and C# via .NET Interactive)...

Changes to the plain text format (merged) and styling (in PR #2610) yields the following, which is an improvement. But we're still planning to do the expanding treeview-style view soon.