Steve Friedl

So re: the issue with #342, there's another place the array index needed fixed a few lines above:  I'm not sure why mine took a different code path than...

This is definitely a thing, and there's a difference between the textual expansion that @nosami posted (which works), and OP's that includes "Tab to accept"; it's the latter that's not...

This sounds like you might have to enforce this with actual program code; I haven't used the parameter set stuff, but I'm not sure it's flexible enough to do what...

I use this project in almost everything I write; if somebody set up a buy-me-a-coffee or other kind of tip jar, I'm happy to contribute.

You're basically asking for everything after the verb to be included in the `Command` property, with no more parsing of dashes and the like?

I've never seen a mechanism like this, but it would be serviced deep in the tokenizer if it were there. My guess is the best you can do is put...

Alternately, do the check prior to even calling the parser: ``` public static int Main(string [] args) { if (args[0] == "foreach") { // special processing } else { //...

I think reflection looking for an attribute will/can get derived classes of that attribute as well, but this is clearly on me to demonstrate. Will dig in.

I finally got around to digging in, and after making literally one change - remove `sealed` from `OptionAttribute`, this all works super well. The current code does in fact look...