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

Groups > gnu.bash.bug > #11698

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

Show all headers | View raw

Eduardo A. Bustamante López wrote:
> $ 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 
> :-)

Additionally let's say that along the way I killed some other text so
that C-y yanks back that more recently killed text instead of the one
I saved first.  In that case ESC C-y will rotate the kill ring to the
previous killed text.  Repeating ESC C-y again rotates to the one
before it.  So can walk back through until finding the text I want to
yank back.  :-)

Bob

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

Thread

Re: why must bash zap last search string just because we hit ^C? Bob Proulx <bob@proulx.com> - 2015-10-18 15:23 -0600

csiph-web