Re: Bug#379942: zsh: rake completion doesn't work for tasks with colons in their names

Re: Bug#379942: zsh: rake completion doesn't work for tasks with colons in their names

[Clint Adams]

> Certainly. Attached (probably more than is relevant).
> BTW, this is rake 0.7.1-1 from unstable and, as can be probably guessed,
> the Rakefile comes from rails.

See if this fixes it.

Index: Completion/Unix/Command/_rake
===================================================================
RCS file: /cvsroot/zsh/zsh/Completion/Unix/Command/_rake,v
retrieving revision 1.5
diff -u -r1.5 _rake
--- Completion/Unix/Command/_rake	14 Sep 2005 12:45:01 -0000	1.5
+++ Completion/Unix/Command/_rake	7 Aug 2006 03:18:55 -0000
@@ -31,7 +31,7 @@
   ;;
   target)
     local -a targets
-    targets=( ${${(f)"$(_call_program targets $words[1] -sT $opt_args[(I)(-N|--nosearch)] ${(kv)opt_args[(I)(-f|--rakefile)]} 2>/dev/null)"}/(#b)rake ([^ ]##) ##\# (*)/$match[1]:${match[2]:l}} )
+    targets=( ${${(f)"$(_call_program targets $words[1] -sT $opt_args[(I)(-N|--nosearch)] ${(kv)opt_args[(I)(-f|--rakefile)]} 2>/dev/null)"}/(#b)rake ([^ ]##) ##\# (*)/${${match[1]}//:/\\:}:${match[2]:l}} )
     if (( ! ${targets[(I)rake aborted!]} )) then
       _describe -t targets 'rake target' targets && ret=0
     else

Re: Bug#379942: zsh: rake completion doesn't work for tasks with colons in their names

[Nikolai Weibull]

On 8/7/06, Clint Adams <schizo@debian.org> wrote:
> > Certainly. Attached (probably more than is relevant).
> > BTW, this is rake 0.7.1-1 from unstable and, as can be probably guessed,
> > the Rakefile comes from rails.
>
> See if this fixes it.

Not quite.  It presents you with the correct completions, but it won't
actually complete anything beyond the first namespace, or colon.  Try
the following:

rake db

in a ruby-on-rails project directory.  You'll be presented with a
bunch of possible completions, including "db:migrate" and the command
line is completed to

rake db:

(in my setup anyway).  Then, when I type an 'm' and run completion
again, no completions are available.  Actually, after the unique
prefix is completed, i.e., 'db:' no completions are available any
more.

Adding 'r:|[:]=*' to ones matcher-list makes it work, but should this
really be necessary?

  nikolai