[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: why must bash zap last search string just because we hit ^C?
From: |
Bob Proulx |
Subject: |
Re: why must bash zap last search string just because we hit ^C? |
Date: |
Sun, 18 Oct 2015 15:23:15 -0600 |
User-agent: |
Mutt/1.5.24 (2015-08-30) |
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
- Re: why must bash zap last search string just because we hit ^C?, (continued)
- Re: why must bash zap last search string just because we hit ^C?, 積丹尼 Dan Jacobson, 2015/10/17
- Re: why must bash zap last search string just because we hit ^C?, 積丹尼 Dan Jacobson, 2015/10/17
- Re: why must bash zap last search string just because we hit ^C?, 積丹尼 Dan Jacobson, 2015/10/17
- Re: why must bash zap last search string just because we hit ^C?, 積丹尼 Dan Jacobson, 2015/10/17
- Re: why must bash zap last search string just because we hit ^C?, 積丹尼 Dan Jacobson, 2015/10/18
- Re: why must bash zap last search string just because we hit ^C?, 積丹尼 Dan Jacobson, 2015/10/20