On 12/26/06, Axel Liljencrantz <[EMAIL PROTECTED]> wrote: > 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.
Does it? I can't reproduce this - if I press Ctrl-C immediately after the command starts executing, it appears in the history. It would be a very strange bug if it didn't. > 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? > It's very annoying the way it is. When I expect that I'll need the command later, I've grown used to doing "Ctrl-A Ctrl-k" to kill the whole line, but it when I don't and use Ctrl-c, I frequently regret it later :-( I think adding to history is better than kill-whole-line by fish's desing criteria: * discoverabilty: people don't paste when they don't expect the clipboard to contain something useful but they do browse through history. * modality: you don't have to refrain from cut-and-paste until you recall the cancelled command. Personally, I'd be just as happy with kill-whole-line. -- Beni Cherniavsky <[EMAIL PROTECTED]> (I read email only 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
