From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@sunsite.dk
Subject: BARE_GLOB_QUAL
Date: Fri, 5 Oct 2001 16:45:33 +0000 [thread overview]
Message-ID: <1011005164534.ZM32624@candle.brasslantern.com> (raw)
In-Reply-To: <20011005172343.A2872@fysh.org>
On Oct 5, 5:23pm, Zefram wrote:
}
} Bart Schaefer wrote:
} >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?
}
} With your proposed change, you'd have to think about the opposite
} ambiguity too -- a set of glob qualifiers might be interpreted as part of
} a pattern, and you'd sometimes need extra effort to force interpretation
} as glob qualifiers. I recommend sticking with the current, simpler, rule.
That sounds fine to me. In that case the doc for one or both of KSH_GLOB
and BARE_GLOB_QUAL should mention this.
} This is why we made the BARE_GLOB_QUAL option -- we wanted an unambiguous
} syntax for glob qualifiers, that wouldn't get in the way of globbing
} syntax at all. Unfortunately no one's yet come up with a really good
} suggestion.
Hm. We're using (#x) for various values of x to introduce things like
approximate completion, case-insensitive matching, and backrefs. How
about (#q...) for qualifiers? Also (#Q-) could turn off BARE_GLOB_QUAL,
and (#Q+) could turn it on. (I can't decide which of those just (#Q)
should do.)
That would introduce the possibility of having different qualifiers for
different parts of the glob pattern, e.g. `*(#qG)/*(#q.^G)' would list
all plain files not owned by the current effective group that are in
directories that are owned by the current effective group.
Although implementation of that latter suggestion might be rather hairy.
For now, all (#q...) should simply be gathered up and applied at the end
as if they appeared in a single list.
--
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
next parent reply other threads:[~2001-10-05 16:47 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 ` Bart Schaefer [this message]
2001-10-05 16:56 ` BARE_GLOB_QUAL Zefram
2001-10-05 17:20 ` BARE_GLOB_QUAL Bart Schaefer
2001-10-08 12:31 ` compctl -g not working Sven Wischnowsky
2001-10-14 1:45 ` 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=1011005164534.ZM32624@candle.brasslantern.com \
--to=schaefer@brasslantern.com \
--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).