diff options
| -rw-r--r-- | ChangeLog | 5 | ||||
| -rw-r--r-- | Completion/Unix/Command/_perforce | 9 |
2 files changed, 11 insertions, 3 deletions
@@ -1,3 +1,8 @@ +2003-03-12 Peter Stephenson <pws@csr.com> + + * 18344: Completion/Unix/Command/_perforce: tag-order is now + useful after 18299. + 2003-03-12 Doug Kearns <djkea2@mugca.its.monash.edu.au> * unposted: Completion/Debian/Command/_debfoster, 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 |