[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: |
Dennis Williamson |
|
Subject: |
Re: why must bash zap last search string just because we hit ^C? |
|
Date: |
Sat, 17 Oct 2015 22:14:14 -0500 |
On Oct 17, 2015 9:06 PM, "積丹尼 Dan Jacobson" <jidanni@jidanni.org> 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 open a new terminal rather than interrupting an in-progress search.
- why must bash zap last search string just because we hit ^C?, 積丹尼 Dan Jacobson, 2015/10/16
- Re: why must bash zap last search string just because we hit ^C?, Chet Ramey, 2015/10/16
- Re: why must bash zap last search string just because we hit ^C?, 積丹尼 Dan Jacobson, 2015/10/17
- Re: why must bash zap last search string just because we hit ^C?, 積丹尼 Dan Jacobson, 2015/10/17
- Re: why must bash zap last search string just because we hit ^C?, 積丹尼 Dan Jacobson, 2015/10/17
- Re: why must bash zap last search string just because we hit ^C?, 積丹尼 Dan Jacobson, 2015/10/17
- Re: why must bash zap last search string just because we hit ^C?, 積丹尼 Dan Jacobson, 2015/10/18
- Re: why must bash zap last search string just because we hit ^C?, 積丹尼 Dan Jacobson, 2015/10/20