zsh-workers
 help / color / mirror / code / Atom feed
From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.dk
Subject: Re: compctl -g not working
Date: Mon, 8 Oct 2001 14:31:30 +0200	[thread overview]
Message-ID: <15297.40098.68834.268916@gargle.gargle.HOWL> (raw)
In-Reply-To: <1011005161336.ZM32521@candle.brasslantern.com>


[ 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


  parent reply	other threads:[~2001-10-08 12:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20011002225307.A13954@astaroth.sweth.net>
     [not found] ` <87adz976ru.fsf@ceramic.fifi.org>
     [not found]   ` <20011002231841.B14325@astaroth.sweth.net>
     [not found]     ` <1011003040449.ZM25370@candle.brasslantern.com>
     [not found]       ` <20011003001256.B14675@astaroth.sweth.net>
     [not found]         ` <1011003060441.ZM25764@candle.brasslantern.com>
     [not found]           ` <20011003021524.A15356@astaroth.sweth.net>
     [not found]             ` <1011003162422.ZM29481@candle.brasslantern.com>
     [not found]               ` <20011003142330.A16765@astaroth.sweth.net>
     [not found]                 ` <1011004042305.ZM30162@candle.brasslantern.com>
     [not found]                   ` <20011004004307.C18930@astaroth.sweth.net>
     [not found]                     ` <1011005161336.ZM32521@candle.brasslantern.com>
     [not found]                       ` <20011005172343.A2872@fysh.org>
2001-10-05 16:45                         ` BARE_GLOB_QUAL Bart Schaefer
2001-10-05 16:56                           ` BARE_GLOB_QUAL Zefram
2001-10-05 17:20                             ` BARE_GLOB_QUAL Bart Schaefer
2001-10-08 12:31                       ` Sven Wischnowsky [this message]
2001-10-14  1:45                         ` compctl -g not working Bart Schaefer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=15297.40098.68834.268916@gargle.gargle.HOWL \
    --to=wischnow@informatik.hu-berlin.de \
    --cc=zsh-workers@sunsite.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).