From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2126 invoked from network); 5 Aug 1999 16:01:11 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 5 Aug 1999 16:01:11 -0000 Received: (qmail 29989 invoked by alias); 5 Aug 1999 16:01:01 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 7383 Received: (qmail 29978 invoked from network); 5 Aug 1999 16:00:59 -0000 From: "Bart Schaefer" Message-Id: <990805160055.ZM16517@candle.brasslantern.com> Date: Thu, 5 Aug 1999 16:00:55 +0000 In-Reply-To: <9908051407.AA36170@ibmth.df.unipi.it> Comments: In reply to Peter Stephenson "Re: configuration question" (Aug 5, 4:07pm) References: <9908051407.AA36170@ibmth.df.unipi.it> X-Mailer: Z-Mail (5.0.0 30July97) To: zsh-workers@sunsite.auc.dk Subject: Re: configuration question MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Aug 5, 4:07pm, Peter Stephenson wrote: } Subject: Re: configuration question } } Wim Yedema wrote: } > I'd like replace self-insert with a function that automatically } > does something like "history-beginning-search-backward" } } I got the following to work A couple of minor adjustments: predict-on() { zle -N self-insert insert-and-predict zle -N magic-space insert-and-predict } predict-off() { zle -A .self-insert self-insert zle -A .magic-space magic-space } The whole idea is actually pretty cool. } It's interesting what happens if you get predict-off wrong. I'll bet, especially considering that you did. -- Bart Schaefer Brass Lantern Enterprises http://www.well.com/user/barts http://www.brasslantern.com