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

Groups > gnu.bash.bug > #11697

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

Show key headers only | View raw

On Sun, Oct 18, 2015 at 12:01:56PM +0800, 積丹尼 Dan Jacobson wrote:
> >>>>> "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 #.
> 

If I have:

$ some long command I've typed 

And then boss calls: URGENT! Run uptime and tell me the output, I'll:


$ some long command I've typed 

Press Ctrl-u

$ _

Write uptime RET

$ uptime
 11:23:45 up 4 days, 22:39,  4 users,  load average: 0.51, 0.86, 0.75

$ _

Press Ctrl-y

$ some long command I've typed 

:-)

-- 
Eduardo Bustamante
https://dualbus.me/

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

Thread

Re: why must bash zap last search string just because we hit ^C? Eduardo A. Bustamante López <dualbus@gmail.com> - 2015-10-18 11:24 -0500

csiph-web