Well, I found this in the API docs:

By default, the parse() method stops as soon as it reaches -- by itself or anything that the parser doesn't recognize as an option, flag, or option value. If arguments still remain, they go into ArgResults.rest.

Which looks like it can help me today.

After playing around the -- doesn't help me because the tools generate the command-line, and they don't put their args after --.

So I think I need a "ignore unspecified args" option for ArgParser.

Will you accept a patch for such a feature?

cc @munificent.

Args has an option now to ignore unspecified arguments, but not unrecognized options. The former lets you have options that appear after non-option arguments. For example:

$ myapp some/file.txt --option

Args can skip over some/file.txt and parse --option. But it doesn't do that for things that look like options (i.e. a leading "-").

I'd be fine with a patch for the latter too, provided it was an opt-in feature. I'm thinking add a "ignoreUnknownOptions" argument to parse().

Thanks Bob. ignoreUnknownOptions as an opt-IN would work. Good to know you'd accept a patch. :)

Removed Library-Args label.
Added Pkg-Args label.

Now at dart-lang/args#9

Added MovedToGithub label.

This issue has been moved to dart-lang/args#23.