Re: problem with context specification

[Peter Stephenson <p.stephenson@xxxxxxxxxxx>]

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))(