From: Peter Stephenson <p.stephenson@samsung.com>
To: <zsh-users@zsh.org>
Subject: Re: problem with context specification
Date: Tue, 14 Jan 2020 11:52:07 +0000 [thread overview]
Message-ID: <1579002727.4404.37.camel@samsung.com> (raw)
In-Reply-To: <CAHYJk3TUoMLWxMhgOpJz_w-d49HduSEd3q9RzQQoGhq1Z1+csg@mail.gmail.com>
On Mon, 2020-01-13 at 18:46 +0100, Mikael Magnusson wrote:
> You're correct, the documentation for tag-order says:
> "The matcher-list style offers something similar, but it is tested
> very early in the completion system and hence can’t be set for single
> commands nor for more specific contexts."
>
> But arguably it could say this in the documentation for matcher-list instead.
Thanks --- rather than duplicate it's probably better to add
cross-references. But it's all rather a headful to take in however
documented.
pws
diff --git a/Doc/Zsh/compsys.yo b/Doc/Zsh/compsys.yo
index ce3e6ea1e..c2d20ca40 100644
--- a/Doc/Zsh/compsys.yo
+++ b/Doc/Zsh/compsys.yo
@@ -2060,6 +2060,9 @@ specification. The value should be in the form described in
ifzman(the section `Completion Matching Control' in zmanref(zshcompwid))\
ifnzman(noderef(Completion Matching Control))\
. For examples of this, see the description of the tt(tag-order) style.
+
+For notes comparing the use of this and the tt(matcher-list) style, see
+under the description of the tt(tag-order) style.
)
kindex(matcher-list, completion style)
item(tt(matcher-list))(
@@ -2124,6 +2127,9 @@ If there is no current matcher or it is empty, and the option
tt(NO_CASE_GLOB) is in effect, the matching for files is performed
case-insensitively in any case. However, any matcher must
explicitly specify case-insensitive matching if that is required.
+
+For notes comparing the use of this and the tt(matcher) style, see
+under the description of the tt(tag-order) style.
)
kindex(max-errors, completion style)
item(tt(max-errors))(
next prev parent reply other threads:[~2020-01-14 11:53 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 [this message]
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
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=1579002727.4404.37.camel@samsung.com \
--to=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).