On 18/09/06, Axel Liljencrantz <[EMAIL PROTECTED]> wrote: > On 9/18/06, Axel Liljencrantz <[EMAIL PROTECTED]> wrote: > [...] > > > * Allow ``commandline -o CMD`` to tokenize CMD instead of current > > > command line (saving, replacing, tokenizing and restoring amazingly > > > does work but is too ugly). > > > > Definitely. What does -o stand for, cOmmand? If so, I guess --command > > should be the GNU-style name. > > Oops, -o is already taken for tokenizing the output of command line. > How about -I for input? (-i is also already used; why are all the good > switches always taken?) > I don't understand. What do you mean by output/input? Currently you can say ``commandline [OPTIONS] CMD`` to specify a new command line but it's incompatible with ``-o``. I propose to allow the combination with the meaning of tokenizing CMD (but replacing the current command line).
-- Beni Cherniavsky <[EMAIL PROTECTED]>, who can only read email on weekends. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Fish-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fish-users
