From: Peter Stephenson <p.w.stephenson@ntlworld.com>
To: zsh-users@zsh.org
Subject: Re: Explicit colons in zstyle
Date: Fri, 30 Mar 2012 20:41:12 +0100 [thread overview]
Message-ID: <20120330204112.00f969a9@pws-pc.ntlworld.com> (raw)
In-Reply-To: <CABZhJg9hy-gZU-k+GAPMJmQq2hiM7TYBn+pUkoSStx_iJow_mQ@mail.gmail.com>
On Thu, 29 Mar 2012 20:59:25 +0200
Jesper Nygårds <jesper.nygards@gmail.com> wrote:
> Is there something special about how a style should be expressed when
> it relates to "completer"?. I started noticing in some examples from
> The Book, that completer is not treated exactly the same as other
> styles.
>
> Here's the well know most-recent-file example:
>
> zstyle ':completion:most-recent-file::::' completer _menu _files _match
> zstyle ':completion:most-recent-file:*' file-sort modification
> zstyle ':completion:most-recent-file:*' hidden all
> zstyle ':completion:most-recent-file:*' file-patterns '*(.):normal\ files'
>
> Is there a reason why the first line contains so many colons? To me it
> looks like it would be equivalent to the other lines, containing an
> asterisk.
I think the book (Oliver wrote that bit) is just making the point that
the completer style is always looked up with most of the fields empty.
By recognising the fact you can make it match many of the fields
exactly.
The only difference with replace the :::: with :* is that it becomes
according to the rules a less exact match, so that if you happened to
have both definitions the former would take precedence. That's not
something you typically need to worry about.
--
Peter Stephenson <p.w.stephenson@ntlworld.com>
Web page now at http://homepage.ntlworld.com/p.w.stephenson/
next prev parent reply other threads:[~2012-03-30 19:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-29 18:59 Jesper Nygårds
2012-03-30 19:41 ` Peter Stephenson [this message]
2012-03-31 13:35 ` Jesper Nygårds
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=20120330204112.00f969a9@pws-pc.ntlworld.com \
--to=p.w.stephenson@ntlworld.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).