From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 435 invoked from network); 9 Jul 1999 15:08:19 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 9 Jul 1999 15:08:19 -0000 Received: (qmail 3791 invoked by alias); 9 Jul 1999 15:08:12 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 7087 Received: (qmail 3783 invoked from network); 9 Jul 1999 15:08:10 -0000 From: "Bart Schaefer" Message-Id: <990709150731.ZM5309@candle.brasslantern.com> Date: Fri, 9 Jul 1999 15:07:31 +0000 In-Reply-To: <199907090819.KAA13084@beta.informatik.hu-berlin.de> Comments: In reply to Sven Wischnowsky "Re: accept-and-infer-next-history in path completion" (Jul 9, 10:19am) References: <199907090819.KAA13084@beta.informatik.hu-berlin.de> X-Mailer: Z-Mail (5.0.0 30July97) To: Sven Wischnowsky , zsh-workers@sunsite.auc.dk Subject: Re: accept-and-infer-next-history in path completion MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Jul 9, 10:19am, Sven Wischnowsky wrote: } Subject: Re: accept-and-infer-next-history in path completion } } > > This makes accept-and-infer-next-history be treated specially when in } > > menu-selection. It accepts the current match and immediatly starts } > > completion again. } > } > In this case a-a-i-n-h is probably misnomer ... } > something like accept-and-continue-completion would be better. } } Sure it is. I just had to take what's there. I'm a bit (er, a lot) behind on patches ... what's the difference between this and accept-and-menu-complete? And if there is a difference, maybe accept-and-hold would be a better widget to co-opt than a-a-i-n-h? -- Bart Schaefer Brass Lantern Enterprises http://www.well.com/user/barts http://www.brasslantern.com