From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20598 invoked from network); 13 Jun 2000 18:38:49 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 13 Jun 2000 18:38:49 -0000 Received: (qmail 7881 invoked by alias); 13 Jun 2000 18:37:46 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 11880 Received: (qmail 7851 invoked from network); 13 Jun 2000 18:37:45 -0000 From: "Bart Schaefer" Message-Id: <1000613164138.ZM9931@candle.brasslantern.com> Date: Tue, 13 Jun 2000 16:41:38 +0000 In-Reply-To: <200006131124.NAA31140@beta.informatik.hu-berlin.de> Comments: In reply to Sven Wischnowsky "PATCH: expansion" (Jun 13, 1:24pm) References: <200006131124.NAA31140@beta.informatik.hu-berlin.de> X-Mailer: Z-Mail (5.0.0 30July97) To: zsh-workers@sunsite.auc.dk Subject: Re: PATCH: expansion MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Jun 13, 1:24pm, Sven Wischnowsky wrote: } Subject: PATCH: expansion } } Note that I've used the same default value in _expand as it has } elsewhere (`false'), which means that without further configuring, } this now behaves differently. Should we make it default to `true' in } _expand? If it now behaves by default more like the way the old expand-or-complete behaved, then I think we should leave it. Either that or the default should be different depending on whether _expand was used as a completer or called from _expand_word ... hrmm ... -- 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