about summary refs log tree commit diff
path: root/Doc
diff options
context:
space:
mode:
authorTanaka Akira <akr@users.sourceforge.net>2000-03-23 04:08:17 +0000
committerTanaka Akira <akr@users.sourceforge.net>2000-03-23 04:08:17 +0000
commit9f883c9b775c5e60d77bd60f8a3472aaa728e105 (patch)
tree1dbdf68024ae1ca3c90c15e5dad461ff829a57f0 /Doc
parent7ab508430cde0bce2bad7cfacbc4a98b724dca10 (diff)
downloadzsh-9f883c9b775c5e60d77bd60f8a3472aaa728e105.tar.gz
zsh-9f883c9b775c5e60d77bd60f8a3472aaa728e105.tar.xz
zsh-9f883c9b775c5e60d77bd60f8a3472aaa728e105.zip
zsh-workers/10178
Diffstat (limited to 'Doc')
-rw-r--r--Doc/Zsh/compsys.yo10
1 files changed, 8 insertions, 2 deletions
diff --git a/Doc/Zsh/compsys.yo b/Doc/Zsh/compsys.yo
index 4dea57109..e7d9fe9e4 100644
--- a/Doc/Zsh/compsys.yo
+++ b/Doc/Zsh/compsys.yo
@@ -1867,8 +1867,8 @@ on the command line (which may be blank).  If given a numeric argument
 var(N), complete the var(N)th most recently modified file.  Note the
 completion, if any, is always unique.
 )
-findex(_next_tags (^Xn))
-item(tt(_next_tags (^Xn)))(
+findex(_next_tags)
+item(tt(_next_tags))(
 This allows to complete types of matches that are not immediately
 offered because of the setting of the tt(tag-order) style. After a
 normal completion was tried, invoking this command makes the matches
@@ -1878,6 +1878,12 @@ matches selected by tt(_next_tags), the tt(completer) style should
 contain tt(_next_tags) as its first string. With that, the normal key
 binding (normally tt(TAB)) can be used to complete the matches shown
 after the call to tt(_next_tags).
+
+Normally, this command is not bound to a key. To invoke it with, say
+`tt(^Xn)', one would use:
+
+example(zle -C _next_tags complete-word _next_tags
+bindkey '^Xn' _next_tags)
 )
 findex(_read_comp (^X^R))
 item(tt(_read_comp (^X^R)))(