Path: csiph.com!au2pb.net!usenet.blueworldhosting.com!feeder01.blueworldhosting.com!news.glorb.com!usenet.stanford.edu!not-for-mail From: =?utf-8?B?56mN5Li55bC8?= Dan Jacobson Newsgroups: gnu.bash.bug Subject: Re: why must bash zap last search string just because we hit ^C? Date: Sun, 18 Oct 2015 10:06:31 +0800 Lines: 13 Approved: bug-bash@gnu.org Message-ID: References: <87io675lhj.fsf@jidanni.org> NNTP-Posting-Host: lists.gnu.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: usenet.stanford.edu 1445134026 8105 208.118.235.17 (18 Oct 2015 02:07:06 GMT) X-Complaints-To: action@cs.stanford.edu Cc: "bug-bash@gnu.org" , Chester Ramey To: Dennis Williamson Envelope-to: bug-bash@gnu.org DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=jidanni.org; h=from:to:cc :subject:references:date:message-id:mime-version:content-type: content-transfer-encoding; s=jidanni.org; bh=eZ41OYoaa+CwTBEnBA4 NxT1ADfM=; b=YS14vcPJUT+8ymnwKK/icXYqUTV0OPj7D1f9txs+EjP8tO97S1o DWZy+1C1ky8A4TUWFuEfFA+01fGNy4fvKyisXFvbWD8XgOeHj261qeRtM1jjXBaA 9tlz/NrjDYHvlu7zsCuLk7gmMdzfsixl9wsfE99hATHMlpGsKdLhgl7o= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 208.97.132.208 X-BeenThere: bug-bash@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Bug reports for the GNU Bourne Again SHell List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Xref: csiph.com gnu.bash.bug:11686 DW> On Fri, Oct 16, 2015 at 1:50 PM, Chet Ramey wro= te: DW> ^C rudely aborts the entire operation.=C2=A0 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.