From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh Users <zsh-users@zsh.org>
Subject: Re: problem with context specification
Date: Mon, 13 Jan 2020 09:53:10 -0800 [thread overview]
Message-ID: <CAH+w=7YUzi07PkApQd3+O4Sh04BOyzeXNb0qcj1Rf1yva+SFtA@mail.gmail.com> (raw)
In-Reply-To: <1578934576.7311.13.camel@samsung.com>
On Mon, Jan 13, 2020 at 8:57 AM Peter Stephenson
<p.stephenson@samsung.com> wrote:
>
> I've a feeling matcher-list is only run in a very general context, so
> updating per command doesn't work, and you need to use the matcher style
> for more specific cases.
Yes, that's exactly it. matcher-list is an oddball that gets queried
before the individual completers are called, so it never has the
fully-formed context string. It populates the default _matchers array
at the top level of _main_complete, which is then overridden by the
matcher style when _descriptions is called after the context is filled
out.
The documentation comes at this sort of sideways; under matcher-list we find:
It is possible to create match specifications valid for particu-
lar completers by using the third field of the context. This
applies only to completers that override the global
matcher-list, which as of this writing includes only _prefix and
_ignored.
next prev parent reply other threads:[~2020-01-13 21:05 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 [this message]
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
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=7YUzi07PkApQd3+O4Sh04BOyzeXNb0qcj1Rf1yva+SFtA@mail.gmail.com' \
--to=schaefer@brasslantern.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).