zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@csr.com>
To: zsh-workers@sunsite.dk (Zsh hackers list)
Subject: Re: PATCH: Re: Bugs thrown up by _perforce
Date: Wed, 12 Mar 2003 11:48:51 +0000	[thread overview]
Message-ID: <15687.1047469731@csr.com> (raw)
In-Reply-To: "Oliver Kiddle"'s message of "Tue, 11 Mar 2003 14:10:33 +0100." <17223.1047388233@finches.logica.co.uk>

Oliver Kiddle wrote:
> On 25 Feb, Peter wrote:
> > > [_next_tags always inserts an unambiguous completion]
> > >
> 
> This patch is my fix for the first of the problems. From my own usage,
> I'm happy that this is definitely better. If anyone really does want
> _next_tags to insert unambiguous matches, it would be easy to make it
> check the insert-unambiguous style.

The current change seems perfectly reasonable.

I finally got around to testing the other fix; it seems to do what I
want now, thanks (at least in _perforce, which is quite a serious test).
This notes the fact in the _perforce comments.

Index: Completion/Unix/Command/_perforce
===================================================================
RCS file: /cvsroot/zsh/zsh/Completion/Unix/Command/_perforce,v
retrieving revision 1.3
diff -u -r1.3 _perforce
--- Completion/Unix/Command/_perforce	23 Feb 2003 16:06:06 -0000	1.3
+++ Completion/Unix/Command/_perforce	12 Mar 2003 11:45:44 -0000
@@ -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

-- 
Peter Stephenson <pws@csr.com>                  Software Engineer
CSR Ltd., Science Park, Milton Road,
Cambridge, CB4 0WH, UK                          Tel: +44 (0)1223 692070


**********************************************************************
The information transmitted is intended only for the person or
entity to which it is addressed and may contain confidential 
and/or privileged material. 
Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by 
persons or entities other than the intended recipient is 
prohibited.  
If you received this in error, please contact the sender and 
delete the material from any computer.
**********************************************************************


      reply	other threads:[~2003-03-12 11:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-23 16:02 Peter Stephenson
2003-02-24 14:50 ` Oliver Kiddle
2003-02-25 13:07   ` Peter Stephenson
2003-02-26  8:47     ` PATCH: " Oliver Kiddle
2003-03-11 13:10     ` Oliver Kiddle
2003-03-12 11:48       ` Peter Stephenson [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=15687.1047469731@csr.com \
    --to=pws@csr.com \
    --cc=zsh-workers@sunsite.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).