From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6946 invoked from network); 8 Oct 2001 12:31:39 -0000 Received: from sunsite.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 8 Oct 2001 12:31:39 -0000 Received: (qmail 27381 invoked by alias); 8 Oct 2001 12:31:32 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 15975 Received: (qmail 27367 invoked from network); 8 Oct 2001 12:31:31 -0000 From: Sven Wischnowsky MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15297.40098.68834.268916@gargle.gargle.HOWL> Date: Mon, 8 Oct 2001 14:31:30 +0200 To: zsh-workers@sunsite.dk Subject: Re: compctl -g not working In-Reply-To: <1011005161336.ZM32521@candle.brasslantern.com> References: <20011002225307.A13954@astaroth.sweth.net> <87adz976ru.fsf@ceramic.fifi.org> <20011002231841.B14325@astaroth.sweth.net> <1011003040449.ZM25370@candle.brasslantern.com> <20011003001256.B14675@astaroth.sweth.net> <1011003060441.ZM25764@candle.brasslantern.com> <20011003021524.A15356@astaroth.sweth.net> <1011003162422.ZM29481@candle.brasslantern.com> <20011003142330.A16765@astaroth.sweth.net> <1011004042305.ZM30162@candle.brasslantern.com> <20011004004307.C18930@astaroth.sweth.net> <1011005161336.ZM32521@candle.brasslantern.com> X-Mailer: VM 6.92 under 21.1 (patch 3) "Acadia" XEmacs Lucid [ moved to -workers ] Bart Schaefer wrote: > ... > > The reason that "some other places" does not include `compctl -s' is > because -s actually *does* pass the string through the lexer again, > whereas -g passes it only through the tokenizer. > > So the questions (hey, zsh-workers) are: > > Should we fix `compctl -g' so that it behaves like "ordinary" globbing? > (I have a suggested implementation that I won't go into here.) Would be fine with me. (I really don't care about compctl anymore ;-) > Should we make BARE_GLOB_QUAL a bit smarter so that it knows about > KSH_GLOB and looks back one more character to see if what precedes the > open-paren token is one of the ksh-glob-chars? (It already treats a > `|' inside the parens as indicative of a glob alternation rather than > a list of qualifiers.) I'm with Zefram here. Bye Sven -- Sven Wischnowsky wischnow@informatik.hu-berlin.de