From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-users@sunsite.dk
Subject: Re: Help w/compctl & ksh_glob
Date: Mon, 18 Aug 2003 15:58:13 +0000 [thread overview]
Message-ID: <1030818155813.ZM12975@candle.brasslantern.com> (raw)
In-Reply-To: <20030818060257.GA15930@bebop.thehutt.org>
On Aug 18, 2:02am, Jerry A! wrote:
} Subject: Re: Help w/compctl & ksh_glob
}
} : The documentation for 'compctl -g' may have part of the answer:
} :
} : [...] More than one pattern may be
} : given separated by blanks. (Note that brace expansion is _not_
} : part of globbing. Use the syntax `(either|or)' to match
} : alternatives.)
}
} Actually, {} globbing is valid ksh93 syntax. It's not valid ksh88
} syntax. But I've always pictured zsh's ksh emulation as ksh93
} emulation.
It's valid syntax, but it's not _globbing_ syntax. The meaning of
*.+(b{oo,ar,az}|quu|txt)
is to expand the expression to the three words
*.+(boo|quu|txt) *.+(bar|quu|txt) *.+(baz|quu|txt)
Only _after_ that expansion has occured does globbing apply.
You can see why that must be the case if you consider an expression
*.+(b{oo,a/r,/az}|quu|txt)
which probably results in two invalid glob patterns (it does in zsh,
at least, because alternatives within (|) can't cross directories), but
one pattern which still produces matches. If brace expansion were part
of globbing, the entire expression would be invalid.
In the case of 'compctl -g', globbing is applied directly to the string
without first performing brace expansion, so you must use an additional
layer of (|).
} : However, the real problem is something to do with the SH_GLOB option,
}
} This got the wheel's turning. Turn's out that 'emulate ksh' turns on
} 'SH_GLOB', which in turns disables (|) globbing.
That's not precisely what's happening, because as I said the (|) pattern
works as expected when it's used on the command line (or at least, it
does for me); it fails only in the compctl arguments. I haven't been
able to figure out why yet.
prev parent reply other threads:[~2003-08-18 15:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-16 6:59 Jerry A!
2003-08-16 16:08 ` Oliver Kiddle
2003-08-16 17:07 ` Bart Schaefer
2003-08-18 6:02 ` Jerry A!
2003-08-18 15:58 ` Bart Schaefer [this message]
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=1030818155813.ZM12975@candle.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-users@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).