Re: [Fish-users] multiline editing issue with mac Terminal.app.

2007-02-25 Thread Axel Liljencrantz
On 2/26/07, Mike Roberts <[EMAIL PROTECTED]> wrote: > there's a couple of problems with the multiline mode of the editor: > > * when my command line spills onto the next line, an ellipsis is put on > the second line and i get another ellipsis on the third line that's > indented. is the intent to ha

[Fish-users] multiline editing issue with mac Terminal.app.

2007-02-25 Thread Mike Roberts
there's a couple of problems with the multiline mode of the editor: * when my command line spills onto the next line, an ellipsis is put on the second line and i get another ellipsis on the third line that's indented. is the intent to have the first ellipsis complete the first line? * subsequen

Re: [Fish-users] Things that keep my from switching to fish.

2007-02-25 Thread Brendan Rankin
Axel Liljencrantz <[EMAIL PROTECTED]> writes: > I would just like to complete Philips excellent answer by explaining > _why_ fish doesn't implement !! and friends. The reason is that they > don't give you any information about what the output will be until you > execute the program. zsh gives you

Re: [Fish-users] Things that keep my from switching to fish.

2007-02-25 Thread Axel Liljencrantz
On 2/23/07, Brendan Rankin <[EMAIL PROTECTED]> wrote: > Overall, I like the principles that fish employs, however, I can't seem to > figure out how to easily access past commands and/or command's arguments using > !$, !!, etc. > > Can this be easily done? If so, how? If not, why not? I would jus