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 23:40 -0400
Message-ID	<mailman.537.1445139644.7904.bug-bash@gnu.org> (permalink)
References	<87io675lhj.fsf@jidanni.org> <87bnbwq462.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:

>>>>>> "CFAJ" == Chris F A Johnson <chris@cfajohnson.com> writes:
>
> CFAJ> Or just press UP (as many times as necessary) and RET.
>
> That won't get me to a $ prompt.
> I want to suspend my search and resume it later.

   ^Z then fg

-- 
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 23:40 -0400

csiph-web