about summary refs log tree commit diff
path: root/Completion/Unix
diff options
context:
space:
mode:
authorPeter Stephenson <pws@users.sourceforge.net>2003-03-12 12:04:32 +0000
committerPeter Stephenson <pws@users.sourceforge.net>2003-03-12 12:04:32 +0000
commit9ba4f4af9c73f296d32a64c7458542f02f701c41 (patch)
treeef52a9c0fee77f58baa08722497e05cf7552a1bb /Completion/Unix
parentaa09c3c859d4028d33fb3365d583f89eef7cca2b (diff)
downloadzsh-9ba4f4af9c73f296d32a64c7458542f02f701c41.tar.gz
zsh-9ba4f4af9c73f296d32a64c7458542f02f701c41.tar.xz
zsh-9ba4f4af9c73f296d32a64c7458542f02f701c41.zip
18344: note in _perforce that tag-order now works.
Diffstat (limited to 'Completion/Unix')
-rw-r--r--Completion/Unix/Command/_perforce9
1 files changed, 6 insertions, 3 deletions
diff --git a/Completion/Unix/Command/_perforce b/Completion/Unix/Command/_perforce
index 555bd9e51..b14ab25fb 100644
--- a/Completion/Unix/Command/_perforce
+++ b/Completion/Unix/Command/_perforce
@@ -63,10 +63,13 @@
 # typing @ or # removes the space which was automatically added.
 # The context used has `at-suffix' or `hash-suffix' in the position
 # before the tag to indicate suffix completion (as always, ^Xh will
-# show you all possible contexts).  This should make it possible
+# show you all possible contexts).  This makes it possible
 # to select changes, dates, labels and clients using the tag-order
-# style, but unfortunately there is a bug which stops any tags afer
-# the first group from being displayed.
+# style.  For example,
+#    zstyle ':completion:*:p4-*:at-suffix:*' tag-order changes '*'
+# will force all completion after `@' to show changes first.  Executing
+# _next_tags (usually ^x^n) will cycle between that and the remaining
+# tags (dates, labels, clients).
 #
 # A # is automatically quoted when handled in this way; if the file is
 # typed by hand or the completion didn't finish (e.g. you typed a character