From: Roderick Schertler <roderick@gate.net>
To: schaefer@nbn.com
Cc: Zsh users mailing list <zsh-users@math.gatech.edu>
Subject: Re: How to kill string but leave it in history?
Date: 16 Jan 1997 14:21:28 -0500 [thread overview]
Message-ID: <pzenfl1l53.fsf@eeyore.ibcinc.com> (raw)
In-Reply-To: <970116102141.ZM18533@candle.brasslantern.com>
On Thu, 16 Jan 1997 10:21:41 -0800, "Bart Schaefer" <schaefer@candle.brasslantern.com> said:
>
> Or push-line-or-edit, which acts like push-line at the PS1 prompt, but
> at the PS2 prompt acts like push-input followed by get-line.
Jeez, how did I miss when that one got added? (Or, cough, how did I
miss it two entries under push-input this morning?) I'd suggest this
doc change over the other one.
--- Doc/zshparam.man.~1~ Tue Aug 13 16:24:13 1996
+++ Doc/zshparam.man Thu Jan 16 14:15:05 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-line-or-edit\fP editor command.
.TP
.B PS3
Selection prompt used within a \fBselect\fP loop.
--
Roderick Schertler
roderick@gate.net
prev parent reply other threads:[~1997-01-16 19:24 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
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 [this message]
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=pzenfl1l53.fsf@eeyore.ibcinc.com \
--to=roderick@gate.net \
--cc=schaefer@nbn.com \
--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).