Eric Wilhelm wrote:
If this is the case, then the cat to be skinned is a couple of steps to the left, since an alias override is a different beast than a config-file override (and not having any way to tell them apart isn't going to help either.)
I don't see what makes them so different -- for this discussion, who cares whether the options are saved in a config file or an alias? And I still don't understand what this common situation is in which you see users typing "--foo --no-foo" or "--no-foo --foo", or what you think they mean by it.
The only reason I can imagine it maybe happening would be if because of frequent use you have a "finger macro" for "command --foo" or "command --no-foo", and have already typed it before you realize that this time you want the opposite of your usual option. Then rather than backspacing you might type the other option. But in that case the desired behavior would be exactly the same as the desired behavior for the alias override case -- for the last option to take precedence.
-- Keith C. Ivey <[EMAIL PROTECTED]> Washington, DC
