mirror of
git://git.code.sf.net/p/zsh/code
synced 2025-01-30 15:02:18 +01:00
43602: Clarify behaviour of compdef -p
This commit is contained in:
parent
f19266cf99
commit
995a56cf01
2 changed files with 9 additions and 1 deletions
|
@ -1,3 +1,7 @@
|
|||
2018-10-10 dana <dana@dana.is>
|
||||
|
||||
* 43602: Doc/Zsh/compsys.yo: Clarify behaviour of `compdef -p`
|
||||
|
||||
2018-10-10 Peter Stephenson <p.stephenson@samsung.com>
|
||||
|
||||
* unposted: Test/C03traps.ztst: Another couple of tests for
|
||||
|
|
|
@ -489,7 +489,11 @@ The parameter tt($_compskip) may be set by any function defined for a
|
|||
pattern context. If it is set to a value containing the substring
|
||||
`tt(patterns)' none of the pattern-functions will be called; if it is
|
||||
set to a value containing the substring `tt(all)', no other function
|
||||
will be called.
|
||||
will be called. Setting tt($_compskip) in this manner is of particular
|
||||
utility when using the tt(-p) option, as otherwise the dispatcher will
|
||||
move on to additional functions (likely the default one) after calling
|
||||
the pattern-context one, which can mangle the display of completion
|
||||
possibilities if not handled properly.
|
||||
|
||||
The form with tt(-k) defines a widget with the same name as the var(function)
|
||||
that will be called for each of the var(key-sequence)s; this is like the
|
||||
|
|
Loading…
Reference in a new issue