compdef weirdness with function

compdef weirdness with function

[Ian Langworth]

If I add a completion definition for some arbitrary, undefined symbol,

   % compdef _perl_modules foo

The completion works normally:

   % foo Acme::<Tab>
   Acme::Bleach        Acme::Magpie        Acme::Morse
   Acme::DWIM          Acme::Magpie::l33t

However, if I then define foo:

  % foo () { echo "args are: $*" }

The completion stops working, even if I re-execute the compdef command
above. What am I doing wrong?

--
Ian Langworth

Re: compdef weirdness with function

[Bart Schaefer]

On Feb 11,  2:57pm, Ian Langworth wrote:
}
} If I add a completion definition for some arbitrary, undefined symbol,
} 
}    % compdef _perl_modules foo

The problem is with _perl_modules.  It expects all commands for which it
complete to be synonyms for perl; it's attempting to run

	foo -e 'print @INC'

to find the include-path for the modules to complete.  When foo does not
exist it falls back to

	perl -e 'print @INC'

but when foo does exist and does not behave like perl, it simply fails.

Re: compdef weirdness with function

[Ian Langworth]

On 2/11/06, Bart Schaefer <schaefer@brasslantern.com> wrote:

> On Feb 11,  2:57pm, Ian Langworth wrote:
> }
> } If I add a completion definition for some arbitrary, undefined symbol,
> }
> }    % compdef _perl_modules foo
>
> The problem is with _perl_modules.  It expects all commands for which it
> complete to be synonyms for perl; it's attempting to run
>
>         foo -e 'print @INC'

Weird and gross. Thanks :)

I've added an if [ "$1" = "-e" ] to my function as a workaround.

--
Ian Langworth