> I can definitely see the benefit of using it that way, however I think > its > incorrect, and just exploiting a flaw in the complete command. If you run 'complete --help' and check examples you will see the usage of command arguments with su. I think that it was done intentionally and is not a flaw. But that is not for sure.
> There should be a distinction between option arguments and command > arguments, and given the explanation in the help: > > OPTION_ARGUMENTS is parameter containing a space-separated list of > possible option-arguments, which may contain subshells > > I would say '-a' is only to be used for option arguments. > A new flag could be created for the use cases you describe above. > (Of course it could be done the other way around as well, that does not > really matter, as long as the help is updated and reflects the behavior) This looks sane. And everything that should be done for it is to stop fish calling '-a' script when calling completion of 'cmd -'. Just like Sanskrit Fritz have written in first message. Maxim ------------------------------------------------------------------------------ For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 _______________________________________________ Fish-users mailing list Fish-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fish-users