bug-bash
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: why must bash zap last search string just because we hit ^C?


From: Chris F.A. Johnson
Subject: Re: why must bash zap last search string just because we hit ^C?
Date: Sat, 17 Oct 2015 22:23:20 -0400 (EDT)
User-agent: Alpine 2.10 (DEB 1266 2009-07-14)

On Sun, 18 Oct 2015, 積丹尼 Dan Jacobson wrote:

DW> On Fri, Oct 16, 2015 at 1:50 PM, Chet Ramey <chet.ramey@case.edu> wrote:

DW>     ^C rudely aborts the entire operation.  Why assume you want to save any
DW>     of the context?

Because I got a phone call: the boss asked me to execute a shell
command. I used ^C to get myself back to a prompt so I could type in the
command. Now I want to resume searching and must type my
^Rlong_search_string all over again.
OK I suppose I can train myself to do ^A # RET or ESC ESC # instead.

Or just press UP (as many times as necessary) and RET.


--
Chris F.A. Johnson, <http://cfajohnson.com>

reply via email to

[Prev in Thread] Current Thread [Next in Thread]