From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13796 invoked from network); 16 Jan 1997 18:16:57 -0000 Received: from euclid.skiles.gatech.edu (list@130.207.146.50) by coral.primenet.com.au with SMTP; 16 Jan 1997 18:16:57 -0000 Received: (from list@localhost) by euclid.skiles.gatech.edu (8.7.3/8.7.3) id NAA05621; Thu, 16 Jan 1997 13:19:26 -0500 (EST) Resent-Date: Thu, 16 Jan 1997 13:15:11 -0500 (EST) From: "Bart Schaefer" Message-Id: <970116102141.ZM18533@candle.brasslantern.com> Date: Thu, 16 Jan 1997 10:21:41 -0800 In-Reply-To: Peter Stephenson "Re: How to kill string but leave it in history?" (Jan 16, 2:54pm) References: <199701161354.OAA12628@sgi.ifh.de> <13945.199701161440@stone.dcs.warwick.ac.uk> <25008.199701161637@stone.dcs.warwick.ac.uk> In-Reply-To: Roderick Schertler "Re: How to kill string but leave it in history?" (Jan 16, 11:27am) In-Reply-To: Zefram "Re: How to kill string but leave it in history?" (Jan 16, 4:37pm) Reply-To: schaefer@nbn.com X-Mailer: Z-Mail (4.0b.820 20aug96) To: Zsh users mailing list Subject: Re: How to kill string but leave it in history? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Resent-Message-ID: <"mRSx93.0.lL1.l0dto"@euclid> Resent-From: zsh-users@math.gatech.edu X-Mailing-List: archive/latest/617 X-Loop: zsh-users@math.gatech.edu X-Loop: zsh-workers@math.gatech.edu Precedence: list Resent-Sender: zsh-workers-request@math.gatech.edu On Jan 16, 4:37pm, Zefram wrote: } Subject: Re: How to kill string but leave it in history? } } Roderick Schertler wrote: } >Which reminds me, it has always bugged me that if zsh creates a } >continuation line (like } > } > $ print "foo } > dquote> _ } > } >) I can't go from the dquote> line back up to the first line } } Yes, this is what push-input is for. 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. (Saves some vertical space and one or two keystrokes.) In answer to the original query, this *ought* to work, and does if you type the keystrokes by hand: bindkey '\eq' push-line-or-edit bindkey -s '^X^H' '\eq\e< print -s ^@\e>\e"^M' For some reason, though, the right-hand-side of the ^X^H binding stops as soon as either of push-input or push-line-or-edit is executed. I.e., the binding above acts like "bindkey -s '^X^H' '\eq'" -- all the trailing stuff is dropped. I presume that's a bug in push-input .... -- Bart Schaefer Brass Lantern Enterprises http://www.well.com/user/barts http://www.nbn.com/people/lantern