From: Bart Schaefer <schaefer@brasslantern.com>
To: Peter Stephenson <p.stephenson@samsung.com>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: problem with context specification
Date: Tue, 14 Jan 2020 10:34:13 -0800 [thread overview]
Message-ID: <CAH+w=7aQ4HctYb81RuMVDb-AgzXPrccROx=pJtvWUTtWBs6xrw@mail.gmail.com> (raw)
In-Reply-To: <1579025111.4404.61.camel@samsung.com>
On Tue, Jan 14, 2020 at 10:06 AM Peter Stephenson
<p.stephenson@samsung.com> wrote:
>
> On Tue, 2020-01-14 at 16:45 +0000, Daniel Shahaf wrote:
> > > I assume the stars are for matching every possible value for that segment,
> > No. An asterisk matches zero or more characters, _including colons_.
>
> This can certainly be a right pain.
It's important to remember that the colons are strictly a completion
system convention -- they have nothing to do with the semantics of
zstyle itself, which can use any sort of context patterns and style
names. That's why completion styles explicitly begin with the fixed
string ":completion:". I even spent a while experimenting with using
it to construct an object hierarchy for a message-passing programming
style (too slow to be more than a curiosity).
next prev parent reply other threads:[~2020-01-14 18:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200113164758eucas1p17ea364450eec705f49edaa8fb69fa65b@eucas1p1.samsung.com>
2020-01-13 16:46 ` Pier Paolo Grassi
2020-01-13 16:56 ` Peter Stephenson
2020-01-13 17:46 ` Mikael Magnusson
2020-01-14 11:52 ` Peter Stephenson
2020-01-13 17:53 ` Bart Schaefer
2020-01-13 17:06 ` Daniel Shahaf
2020-01-13 17:41 ` [PATCH] docs: Add an example of setting and querying zstyles (was: Re: problem with context specification) Daniel Shahaf
2020-01-14 15:59 ` problem with context specification Pier Paolo Grassi
2020-01-14 16:45 ` Daniel Shahaf
2020-01-14 17:55 ` Pier Paolo Grassi
2020-01-14 18:05 ` Peter Stephenson
2020-01-14 18:34 ` Bart Schaefer [this message]
2020-01-14 18:50 ` Daniel Shahaf
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='CAH+w=7aQ4HctYb81RuMVDb-AgzXPrccROx=pJtvWUTtWBs6xrw@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=p.stephenson@samsung.com \
--cc=zsh-users@zsh.org \
/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).