Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #11695
| 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 | 2015-10-18 12:01 +0800 |
| Message-ID | <mailman.540.1445140925.7904.bug-bash@gnu.org> (permalink) |
| References | <87io675lhj.fsf@jidanni.org> |
>>>>> "DR" == Dave Rutherford <dave@evilpettingzoo.com> writes: DR> Can you run gnu screen? ^A-c will get you a new shell session in the DR> existing terminal emulator (it will use a new terminal device, though, DR> if that's what you care about.) Let's pretend that I am on a gunk device on a gunk OS and all I have to work with is this one shell and I just want to back out of my search peacefully and resume it later with minimal ado. OK I will do ESC ESC #.
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 12:01 +0800
csiph-web