Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > gnu.bash.bug > #11672

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

Path csiph.com!xmission!news.glorb.com!usenet.stanford.edu!not-for-mail
From 積丹尼 Dan Jacobson <jidanni@jidanni.org>
Newsgroups gnu.bash.bug
Subject why must bash zap last search string just because we hit ^C?
Date Fri, 16 Oct 2015 15:19:20 +0800
Lines 6
Approved bug-bash@gnu.org
Message-ID <mailman.437.1444979997.7904.bug-bash@gnu.org> (permalink)
NNTP-Posting-Host lists.gnu.org
Mime-Version 1.0
Content-Type text/plain
X-Trace usenet.stanford.edu 1444979997 21969 208.118.235.17 (16 Oct 2015 07:19:57 GMT)
X-Complaints-To action@cs.stanford.edu
To bug-bash@gnu.org
Envelope-to bug-bash@gnu.org
DKIM-Signature v=1; a=rsa-sha1; c=relaxed; d=jidanni.org; h=from:to :subject:date:message-id:mime-version:content-type; s= jidanni.org; bh=3mx4rBzjEm/2uyXTPtyouhXTu28=; b=O2Ho/1IHL4RnDBAk hwowxGYGgCTl/1ETOQYsvjuMBCrMBsQEtNMwMSqLD1Ae/mncDBkrTjgzfpC6T8rH pKNR0OwOKk+RcEUlFLp+MfBPGX+Dtlpq+Qr8lFiEcC9CRioHx553w0q67vFnL4Cb 4bqXBQyJ+ttbBiIx+xcn838WGts=
X-detected-operating-system by eggs.gnu.org: GNU/Linux 2.2.x-3.x (no timestamps) [generic]
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 <bug-bash.gnu.org>
List-Unsubscribe <https://lists.gnu.org/mailman/options/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=unsubscribe>
List-Archive <http://lists.gnu.org/archive/html/bug-bash>
List-Post <mailto:bug-bash@gnu.org>
List-Help <mailto:bug-bash-request@gnu.org?subject=help>
List-Subscribe <https://lists.gnu.org/mailman/listinfo/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=subscribe>
Xref csiph.com gnu.bash.bug:11672

Show key headers only | View raw


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?

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


Thread

why must bash zap last search string just because we hit ^C? 積丹尼 Dan Jacobson <jidanni@jidanni.org> - 2015-10-16 15:19 +0800

csiph-web