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

From	"Chris F.A. Johnson" <chris@cfajohnson.com>
Newsgroups	gnu.bash.bug
Subject	Re: why must bash zap last search string just because we hit ^C?
Date	2015-10-17 22:23 -0400
Message-ID	<mailman.532.1445135028.7904.bug-bash@gnu.org> (permalink)
References	<87io675lhj.fsf@jidanni.org> <87fv19orq0.fsf@jidanni.org>

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

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>

Back to gnu.bash.bug | Previous | Next | Find similar

Thread

Re: why must bash zap last search string just because we hit ^C? "Chris F.A. Johnson" <chris@cfajohnson.com> - 2015-10-17 22:23 -0400

csiph-web