Re: Bug#411050: zsh: configure completion doesn't work after --enable-shared

Re: Bug#411050: zsh: configure completion doesn't work after --enable-shared

[Clint Adams]

> If I type:
> 
>   ./configure --enable-shared --en[TAB]
> 
> the completion doesn't work. It seems that the completion code waits
> for a --enable-shared argument. However the argument is optional.

What is the relevant output of ./configure --help ?

Re: Bug#411050: zsh: configure completion doesn't work after --enable-shared

[Vincent Lefevre]

On 2007-02-15 10:20:55 -0500, Clint Adams wrote:
> > If I type:
> > 
> >   ./configure --enable-shared --en[TAB]
> > 
> > the completion doesn't work. It seems that the completion code waits
> > for a --enable-shared argument. However the argument is optional.
> 
> What is the relevant output of ./configure --help ?

  --enable-shared[=PKGS]  build shared libraries [default=yes]

Same problem with --enable-static, where one has:

  --enable-static[=PKGS]  build static libraries [default=yes]

-- 
Vincent Lefèvre <vincent@vinc17.org> - Web: <http://www.vinc17.org/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/>
Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon)

Re: Bug#411050: zsh: configure completion doesn't work after --enable-shared

[Clint Adams]

>   --enable-shared[=PKGS]  build shared libraries [default=yes]
> 
> Same problem with --enable-static, where one has:
> 
>   --enable-static[=PKGS]  build static libraries [default=yes]

I haven't looked at _arguments, but presumably it doesn't understand
this convention.

Re: Bug#411050: zsh: configure completion doesn't work after --enable-shared

[Peter Stephenson]

Clint Adams <clint@zsh.org> wrote:
> >   --enable-shared[=PKGS]  build shared libraries [default=yes]
> > 
> > Same problem with --enable-static, where one has:
> > 
> >   --enable-static[=PKGS]  build static libraries [default=yes]
> 
> I haven't looked at _arguments, but presumably it doesn't understand
> this convention.

This seems to help.

I notice that automatically generated --without-* and --disable-*
option specifiers offer to add an argument, too.  Presumably this is
wrong?

Index: Completion/Base/Utility/_arguments
===================================================================
RCS file: /cvsroot/zsh/zsh/Completion/Base/Utility/_arguments,v
retrieving revision 1.19
diff -u -r1.19 _arguments
--- Completion/Base/Utility/_arguments	10 Oct 2006 21:26:52 -0000	1.19
+++ Completion/Base/Utility/_arguments	16 Feb 2007 14:52:30 -0000
@@ -217,7 +217,11 @@
 	  else
 	    odescr=
 	  fi
-	  opt2=${${opt%%\[\=*}//[^a-zA-Z0-9-]}=${dir}${odescr}
+	  if [[ $opt = (#b)(*)\[\=* ]]; then
+	    opt2=${${match[1]}//[^a-zA-Z0-9-]}=-${dir}${odescr}
+	  else
+	    opt2=${${opt}//[^a-zA-Z0-9-]}=${dir}${odescr}
+	  fi
 	  if [[ "$descr" = :\=* ]]; then
 	    cache+=( "${opt2}::${(L)${opt%\]}#*\=}: " )
 	  elif [[ "$descr" = ::* ]]; then


-- 
Peter Stephenson <pws@csr.com>                  Software Engineer
CSR PLC, Churchill House, Cambridge Business Park, Cowley Road
Cambridge, CB4 0WZ, UK                          Tel: +44 (0)1223 692070


To access the latest news from CSR copy this link into a web browser:  http://www.csr.com/email_sig.php

To get further information regarding CSR, please visit our Investor Relations page at http://ir.csr.com/csr/about/overview