From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12883 invoked from network); 29 May 1999 07:27:06 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 29 May 1999 07:27:06 -0000 Received: (qmail 7433 invoked by alias); 29 May 1999 07:26:51 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 6364 Received: (qmail 7424 invoked from network); 29 May 1999 07:26:50 -0000 From: "Bart Schaefer" Message-Id: <990529072640.ZM27086@candle.brasslantern.com> Date: Sat, 29 May 1999 07:26:40 +0000 In-Reply-To: <199905110939.CAA29206@bebop.clari.net> Comments: In reply to Wayne Davison "Re: PATCH: history improvements for 3.1.5-pws-17" (May 11, 2:39am) References: <199905110939.CAA29206@bebop.clari.net> X-Mailer: Z-Mail (5.0.0 30July97) To: Wayne Davison Subject: Re: PATCH: history improvements for 3.1.5-pws-17 Cc: zsh-workers@sunsite.auc.dk (Zsh hackers list) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Man, I hate getting this far behind. On May 11, 2:39am, Wayne Davison wrote: } Subject: Re: PATCH: history improvements for 3.1.5-pws-17 } } > Hmmm, it might be a good idea to make `zle widget num' override the } > value of $NUMERIC with num when calling a widget. } } I like this -- it makes writing an up-line-or-local-history function } much simpler. Way back in zsh-workers/4103 I griped: ... right now it's completely impossible for a user-defined widget to initiate a history search; "zle history-search-backward" just causes the shell to prompt the user for input, but the widget may already have a string it wants to search for. "history-search-backward string" is the natural way to perform that action. If we're implementing this, why are we limiting it to *numeric* arguments? -- Bart Schaefer Brass Lantern Enterprises http://www.well.com/user/barts http://www.brasslantern.com