From: Oliver Kiddle <okiddle@yahoo.co.uk>
To: zsh-workers@sunsite.dk (Zsh hackers list)
Subject: PATCH: Re: Bugs thrown up by _perforce
Date: Tue, 11 Mar 2003 14:10:33 +0100 [thread overview]
Message-ID: <17223.1047388233@finches.logica.co.uk> (raw)
In-Reply-To: <22979.1046178445@csr.com>
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.
Oliver
Index: Completion/Base/Widget/_next_tags
===================================================================
RCS file: /cvsroot/zsh/zsh/Completion/Base/Widget/_next_tags,v
retrieving revision 1.4
diff -u -r1.4 _next_tags
--- Completion/Base/Widget/_next_tags 26 Feb 2003 16:36:07 -0000 1.4
+++ Completion/Base/Widget/_next_tags 11 Mar 2003 12:59:00 -0000
@@ -1,4 +1,4 @@
-#compdef -k complete-word \C-xn
+#compdef -k list-choices \C-xn
# Main widget.
@@ -96,11 +96,7 @@
_next_tags_pfx="$PREFIX"
_next_tags_sfx="$SUFFIX"
- if [[ -n "$compstate[old_insert]" ]]; then
- ins=1
- else
- ins=unambiguous
- fi
+ ins="${compstate[old_insert]:+1}"
_main_complete _complete _next_tags_completer
next prev parent reply other threads:[~2003-03-11 13:06 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 [this message]
2003-03-12 11:48 ` Peter Stephenson
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=17223.1047388233@finches.logica.co.uk \
--to=okiddle@yahoo.co.uk \
--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).