Ralf Wildenhues wrote:
> * Pádraig Brady wrote on Tue, Nov 03, 2009 at 12:35:05PM CET:
>> --- a/doc/find.texi
>> +++ b/doc/find.texi
>> @@ -3521,6 +3521,15 @@ Use at most @var{max-args} arguments per command
>> line. Fewer than
>> option) is exceeded, unless the @samp{-x} option is given, in which
>> case @code{xargs} will exit.
>>
>> +...@item --max-pr...@r{[}=@var{max-pro...@r{]}
>> +...@itemx -...@r{[}@var{max-pro...@r{]}
>
> With this, `xargs -P0' is ambiguous, and could be `-0 -P' or
> `--max-procs=0'.
Ah right, optional args should be avoided if possible.
I even documented this years ago with xargs as an example :)
http://www.pixelbeat.org/talks/iitui/options.html
The existing xargs options with optional args are deprecated.
BTW, it wouldn't be ambiguous to the program, nor would it
be different than the existing meaning, but as you say,
users could mistakenly do -P0 when they meant -0P.
So I'll make the arg mandatory, but what to choose?
"n" is all I can come up with in my half awake state.
I'll sleep on it.
cheers,
Pádraig.
