Re: why must bash zap last search string just because we hit ^C?
From:
Chet Ramey
Subject:
Re: why must bash zap last search string just because we hit ^C?
Date:
Fri, 16 Oct 2015 14:50:59 -0400
User-agent:
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
On 10/16/15 3:19 AM, 積丹尼 Dan Jacobson wrote:
> Type ^Racb^C^R^R
> (Search backwards for abc, then hit ^C, then try searching backwards
> some more using the last search string.)
>
> My problem is why must bash zap the memory of abc just because we hit ^C?
^C rudely aborts the entire operation. Why assume you want to save any
of the context?
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU chet@case.edu http://cnswww.cns.cwru.edu/~chet/