Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #11686
| Path | csiph.com!au2pb.net!usenet.blueworldhosting.com!feeder01.blueworldhosting.com!news.glorb.com!usenet.stanford.edu!not-for-mail |
|---|---|
| From | 積丹尼 Dan Jacobson <jidanni@jidanni.org> |
| 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 | <mailman.530.1445134026.7904.bug-bash@gnu.org> (permalink) |
| 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" <bug-bash@gnu.org>, Chester Ramey <chet.ramey@case.edu> |
| To | Dennis Williamson <dennistwilliamson@gmail.com> |
| 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 <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:11686 |
Show key headers only | View raw
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.
Back to gnu.bash.bug | Previous | Next | Find similar
Re: why must bash zap last search string just because we hit ^C? 積丹尼 Dan Jacobson <jidanni@jidanni.org> - 2015-10-18 10:06 +0800
csiph-web