From: Philippe Troin <phil@fifi.org>
To: zzapper <david@rayninfo.co.uk>
Cc: zsh-users@zsh.org
Subject: Re: Tip of the day: restoring an aborted command-line
Date: Thu, 02 Jul 2015 16:11:13 -0700 [thread overview]
Message-ID: <1435878673.17325.5.camel@niobium.home.fifi.org> (raw)
In-Reply-To: <XnsA4CBE4DD846E3davidrayninfocouk@80.91.229.13>
On Thu, 2015-07-02 at 21:29 +0000, zzapper wrote:
> Oliver Kiddle <okiddle@yahoo.co.uk> wrote in
> news:30469.1435788779@thecus.kiddle.eu:
>
> > When you abort a command-line with Ctrl-C or whatever, the Zsh line
> > editor sets $ZLE_LINE_ABORTED to the contents of the command-line
> > before it was aborted. Sometimes you might want to recover the aborted
> > line and you could bind a dedicated key to that purpose. The following
>
> >
> > zle-line-init () {
> > if [[ -n $ZLE_LINE_ABORTED ]]; then
> > local savebuf="$BUFFER" savecur="$CURSOR"
> > BUFFER="$ZLE_LINE_ABORTED"
> > CURSOR="$#BUFFER"
> > zle split-undo
> > BUFFER="$savebuf" CURSOR="$savecur"
> > fi
> > }
>
> > Oliver
> is $ZLE_LINE_ABORTED dependent on any autoload? as i have it on cygwin
> but not on centos (both 5.08)
It shouldn't.
I'd like to propose the following enhancement:
zle-line-init () {
if [[ -n $ZLE_LINE_ABORTED ]]; then
_last_aborted_line=$ZLE_LINE_ABORTED
fi
if [[ -n $_last_aborted_line ]]
then
local savebuf="$BUFFER" savecur="$CURSOR"
BUFFER="$_last_aborted_line"
CURSOR="$#BUFFER"
zle split-undo
BUFFER="$savebuf" CURSOR="$savecur"
fi
}
zle -N zle-line-init
zle-line-finish() {
unset _last_aborted_line
}
zle -N zle-line-finish
Now this handle the case when you press Ctrl-C multiple times in a row.
Eg:
zsh% foo=^C
zsh% ^C
zsh% ^C
zsh% <undo>
zsh% foo=
Phil.
next prev parent reply other threads:[~2015-07-02 23:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-01 22:12 Oliver Kiddle
2015-07-02 21:29 ` zzapper
2015-07-02 23:11 ` Philippe Troin [this message]
2015-07-03 2:42 ` Bart Schaefer
2015-07-03 8:56 ` zzapper
2015-07-03 15:49 ` Greg Klanderman
2015-07-05 16:26 ` lilydjwg
2015-07-05 18:43 ` Bart Schaefer
2015-07-05 21:17 ` Mikael Magnusson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1435878673.17325.5.camel@niobium.home.fifi.org \
--to=phil@fifi.org \
--cc=david@rayninfo.co.uk \
--cc=zsh-users@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).