From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13174 invoked from network); 18 Oct 2000 15:39:17 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 18 Oct 2000 15:39:17 -0000 Received: (qmail 1438 invoked by alias); 18 Oct 2000 15:39:12 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 13027 Received: (qmail 1428 invoked from network); 18 Oct 2000 15:39:11 -0000 From: "Bart Schaefer" Message-Id: <1001018153811.ZM4426@candle.brasslantern.com> Date: Wed, 18 Oct 2000 15:38:10 +0000 In-Reply-To: <0G2M00EBTC1Z6M@la-la.cambridgesiliconradio.com> Comments: In reply to Peter Stephenson "Re: parse errors and up-line-or-history" (Oct 18, 10:08am) References: <0G2M00EBTC1Z6M@la-la.cambridgesiliconradio.com> X-Mailer: Z-Mail (5.0.0 30July97) To: zsh-workers@sunsite.auc.dk (Zsh hackers list) Subject: Re: parse errors and up-line-or-history MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Oct 18, 10:08am, Peter Stephenson wrote: } } Bart wrote: } > that anything that won't lex, doesn't make it into the history. } } There was originally a partial fix that the rest of the line gets read in } and stuck on the end of the history without lexing. I haven't looked at } this for a long time, so it may be at the mercy of various flags Aha! It's HIST_REDUCE_BLANKS! Unset that option, and the entire command line makes it into the history. Wayne, are you listening? The other stuff I talked about in 10996, e.g. editing the line from before history expansion was done, still applies. -- Bart Schaefer Brass Lantern Enterprises http://www.well.com/user/barts http://www.brasslantern.com Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net