On 12/20/06, Philip Ganchev <[EMAIL PROTECTED]> wrote: > Hi all > > I just realized that if you start writing a command and press > Control+C, it is not saved in the history, unlike if you press > UpArrow. The same happens if you press Control+C after the command > starts executing. So if you see that your command is erring and > cancel it, you have to retype it. This is especially bad for long, > multiline commands where errors are likely.
Merry Christmas! That is the same as how other shells do it. I can see the use of adding semicompleted commands to the history, but it would also potentially cause a cluttered history. Another option would be to make ^C call kill-whole-line, e.g. add the contents to the killring. Does anybody else have an opinion on this? > > Cheers, > Philip > > ------------------------------------------------------------------------- > 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 > -- 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
