Re: How to kill string but leave it in history?

[Roderick Schertler <roderick@gate.net>]

On Thu, 16 Jan 1997 16:37:52 +0000 (GMT), Zefram <zefram@dcs.warwick.ac.uk> said:
> Roderick Schertler wrote:
>>>
>>> This is exactly what pound-insert is for.  I use it often.
>>
>> It doesn't work for multiline commands, though.
>
> Yes it does.  It adds a # at the beginning of each line.  Or do you
> mean continuation lines?  push-input may help here.

Right, I hadn't clued to the fact that it was continuation lines which
were the problem.  I also hadn't thought of using push-input to edit
back before a continuation, and I even regularly use push-input.
Thanks.  Here's a hint for the documentation which might save others
this trouble.

--- Doc/zshzle.man.~1~	Tue Dec 17 15:14:11 1996
+++ Doc/zshzle.man	Thu Jan 16 12:34:30 1997
@@ -653,6 +653,8 @@
 Next time the editor starts up or is popped with \fBget-line\fP, the
 construct will be popped off the top of the buffer stack and loaded
 into the editing buffer.
+This is currently the best way to edit text above a zsh-forced line
+continuation.
 .TP
 \fBpush-line\fP (^Q ESC-Q ESC-q) (unbound) (unbound)
 Push the current buffer onto the buffer stack and clear
--- Doc/zshparam.man.~1~	Tue Aug 13 16:24:13 1996
+++ Doc/zshparam.man	Thu Jan 16 12:35:52 1997
@@ -685,6 +685,8 @@
 Recognizes the same escape sequences as \fB$PS1\fP.
 The default is "%_> ", which displays any shell constructs or quotation
 marks which are currently being processed.
+The best way to edit the continuation text along with the initial part
+of the command is to use the \fBpush-input\fP editor command.
 .TP
 .B PS3
 Selection prompt used within a \fBselect\fP loop.

-- 
Roderick Schertler
roderick@gate.net