diff options
author | Oliver Kiddle <opk@zsh.org> | 2016-06-22 01:37:07 +0200 |
---|---|---|
committer | Oliver Kiddle <opk@zsh.org> | 2016-06-22 01:37:07 +0200 |
commit | e83489fc4ba168abeb5ea7e23e64383fed181ed3 (patch) | |
tree | b573a21ddbccc2adf8132166b2a7b5a22d6bec6d /Doc/Zsh | |
parent | 139a4dbe07728a22dcb120d1ca9ff3cdae98471a (diff) | |
download | zsh-e83489fc4ba168abeb5ea7e23e64383fed181ed3.tar.gz zsh-e83489fc4ba168abeb5ea7e23e64383fed181ed3.tar.xz zsh-e83489fc4ba168abeb5ea7e23e64383fed181ed3.zip |
38714: add x: syntax to match specs to make it possible to disable match specs hardcoded in completion functions
Diffstat (limited to 'Doc/Zsh')
-rw-r--r-- | Doc/Zsh/compsys.yo | 5 | ||||
-rw-r--r-- | Doc/Zsh/compwid.yo | 7 |
2 files changed, 10 insertions, 2 deletions
diff --git a/Doc/Zsh/compsys.yo b/Doc/Zsh/compsys.yo index c97f80f27..fb0abcef3 100644 --- a/Doc/Zsh/compsys.yo +++ b/Doc/Zsh/compsys.yo @@ -2023,8 +2023,9 @@ only be performed with the `tt(*)' inserted. kindex(matcher, completion style) item(tt(matcher))( This style is tested separately for each tag valid in the current -context. Its value is tried before any match specifications given by the -tt(matcher-list) style. It should be in the form described in +context. Its value is placed before any match specifications given by the +tt(matcher-list) style so can override them via the use of an tt(x:) +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. diff --git a/Doc/Zsh/compwid.yo b/Doc/Zsh/compwid.yo index c01763316..1cc94bf95 100644 --- a/Doc/Zsh/compwid.yo +++ b/Doc/Zsh/compwid.yo @@ -913,6 +913,13 @@ line and trial completion patterns are anchored on the right side. Here an empty var(ranchor) and the tt(e) and tt(E) forms force the match to the end of the command line or trial completion string. ) +item(tt(x:))( +This form is used to mark the end of matching specifications: +subsequent specifications are ignored. In a single standalone list +of specifications this has no use but where matching specifications +are accumulated, such as from nested function calls, it can allow one +function to override another. +) enditem() Each var(lpat), var(tpat) or var(anchor) is either an empty string or |