zsh-users
 help / color / mirror / code / Atom feed
From: Zefram <zefram@dcs.warwick.ac.uk>
To: roderick@gate.net (Roderick Schertler)
Cc: zefram@dcs.warwick.ac.uk, borsenkow.msk@sni.de,
	zsh-users@math.gatech.edu
Subject: Re: How to kill string but leave it in history?
Date: Thu, 16 Jan 1997 16:37:52 +0000 (GMT)	[thread overview]
Message-ID: <25008.199701161637@stone.dcs.warwick.ac.uk> (raw)
In-Reply-To: <pzg2011t6l.fsf@eeyore.ibcinc.com> from "Roderick Schertler" at Jan 16, 97 11:27:46 am

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.

>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

Yes, this is what push-input is for.

-zefram


  reply	other threads:[~1997-01-16 16:39 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 [this message]
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=25008.199701161637@stone.dcs.warwick.ac.uk \
    --to=zefram@dcs.warwick.ac.uk \
    --cc=borsenkow.msk@sni.de \
    --cc=roderick@gate.net \
    --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).