On 9/21/06, Beni Cherniavsky <[EMAIL PROTECTED]> wrote: > 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).
What I meant was that the -o switch is already used. It causes the output of the commandline builtin to be tokenized, so that each argument or command is printed on a separate line. I've implemented the requested functionality using the -I/--input switch instead: fish>commandline -I "foo;bar" -p bar I've also added getting/setting the cursor using the -C/--cursor switch. 'commandline -C' will print the current cursor position, and 'commandline -C 3' will set it to 3. > > -- > Beni Cherniavsky <[EMAIL PROTECTED]>, who can only read email on weekends. > -- Axel ------------------------------------------------------------------------- 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
