PATCH: Re: Bugs thrown up by _perforce

[Oliver Kiddle <okiddle@xxxxxxxxxxx>]

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