From: Roderick Schertler <roderick@gate.net>
To: Zefram <zefram@dcs.warwick.ac.uk>
Cc: borsenkow.msk@sni.de, zsh-users@math.gatech.edu
Subject: Re: How to kill string but leave it in history?
Date: 16 Jan 1997 11:27:46 -0500 [thread overview]
Message-ID: <pzg2011t6l.fsf@eeyore.ibcinc.com> (raw)
In-Reply-To: <13945.199701161440@stone.dcs.warwick.ac.uk>
On Thu, 16 Jan 1997 14:40:54 +0000 (GMT), Zefram <zefram@dcs.warwick.ac.uk> said:
> Andrej Borsenkow wrote:
>>
>> So - is there any way to cancel current command line but leave it in
>> history?
>
> This is exactly what pound-insert is for. I use it often.
It doesn't work for multiline commands, though. Here's a binding (set
up for vi mode) which works if none of the editing lines were zsh-forced
continuations (which I don't understand, seems like a bug):
bindkey -a -s q '\M-xpush-input\C-maread -z _buf; print -s $_buf\C-m'
Which reminds me, it has always bugged me that if zsh creates a
continuation line (like
$ print "foo<return>
dquote> _
) I can't go from the dquote> line back up to the first line (my
workaround is to get onto a blank line and interrupt, then pull up the
history). Is it just me? Is there a way not to have this happen?
--
Roderick Schertler
roderick@gate.net
next prev parent reply other threads:[~1997-01-16 16:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-01-16 10:59 Andrej Borsenkow
1997-01-16 12:15 ` Peter Stephenson
1997-01-16 13:36 ` Andrej Borsenkow
1997-01-16 13:54 ` Peter Stephenson
1997-01-16 14:02 ` Juergen Christoffel
1997-01-16 14:40 ` Zefram
1997-01-16 16:27 ` Roderick Schertler [this message]
1997-01-16 16:37 ` Zefram
1997-01-16 17:41 ` Roderick Schertler
[not found] ` <pws@ifh.de>
[not found] ` <roderick@gate.net>
[not found] ` <zefram@dcs.warwick.ac.uk>
1997-01-16 18:21 ` Bart Schaefer
1997-01-16 18:39 ` Zefram
1997-01-17 9:05 ` Bart Schaefer
1997-01-16 19:21 ` Roderick Schertler
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=pzg2011t6l.fsf@eeyore.ibcinc.com \
--to=roderick@gate.net \
--cc=borsenkow.msk@sni.de \
--cc=zefram@dcs.warwick.ac.uk \
--cc=zsh-users@math.gatech.edu \
/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).