Completion on simple commande

Completion on simple commande

[Michel]

Hi,

I use an zsh function to launch the graphical application. But I don't
know how have the completion on my function.

My function is :
function start (){
    $@ > /dev/null 2> /dev/null &
}

And I want can type :
start fire<tab>

To launch firefox. In bash I know the "complete" commande but I don't
know the zsh metode.

Can you help me, please ?
_____________________
Michel BARRET

Re: Completion on simple commande

[Peter Stephenson]

On Thu, 12 Aug 2010 11:11:11 +0200
Michel <michel.barret@gmail.com> wrote:
> I use an zsh function to launch the graphical application. But I don't
> know how have the completion on my function.
> 
> My function is :
> function start (){
>     $@ > /dev/null 2> /dev/null &
> }
> 
> And I want can type :
> start fire<tab>

"man zshcompsys" is the place to start, but working that way it'll take a
while before you get to the point where you can answer questions like this.

First you'll need to start the completion system; it's not clear if you've done
that.  If you haven't, put this in your ~/.zshrc:

autoload -Uz compinit
compinit

Then the simplest answer to the immediate question is to add the following
line:

compdef _precommand start

That makes "start" behave like other command words that take a complete
command line following.

By the way, you might want to put the $@ in double quotes:

function start (){
    "$@" > /dev/null 2> /dev/null &
}

The difference is that this won't remove any zero-length arguments to the
command, e.g. a '' on the command line.  That's not a typical problem with
the sort of use you have, however.

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


Member of the CSR plc group of companies. CSR plc registered in England and Wales, registered number 4187346, registered office Churchill House, Cambridge Business Park, Cowley Road, Cambridge, CB4 0WZ, United Kingdom

Re: Completion on simple commande

[Frank Terbeck]

Michel wrote:
> I use an zsh function to launch the graphical application. But I don't
> know how have the completion on my function.
>
> My function is :
> function start (){
>     $@ > /dev/null 2> /dev/null &
> }

You probably want to use "$@" (double-quoted) here.

> And I want can type :
> start fire<tab>
>
> To launch firefox. In bash I know the "complete" commande but I don't
> know the zsh metode.

compdef _precommand start

That will make the command-specific version work, too.

Regards, Frank

-- 
In protocol design, perfection has been reached not when there is
nothing left to add, but when there is nothing left to take away.
                                                  -- RFC 1925

Re: Completion on simple commande

[Michel]

2010/8/12 Peter Stephenson <Peter.Stephenson@csr.com>:
> On Thu, 12 Aug 2010 11:11:11 +0200
> Michel <michel.barret@gmail.com> wrote:
>> I use an zsh function to launch the graphical application. But I don't
>> know how have the completion on my function.
>>
>> My function is :
>> function start (){
>>     $@ > /dev/null 2> /dev/null &
>> }
>>
>> And I want can type :
>> start fire<tab>
>
> "man zshcompsys" is the place to start, but working that way it'll take a
> while before you get to the point where you can answer questions like this.
>
> First you'll need to start the completion system; it's not clear if you've done
> that.  If you haven't, put this in your ~/.zshrc:
>
> autoload -Uz compinit
> compinit

This configuration is already applied.

> Then the simplest answer to the immediate question is to add the following
> line:
>
> compdef _precommand start

Thanks it's exactly that !

> That makes "start" behave like other command words that take a complete
> command line following.
>
> By the way, you might want to put the $@ in double quotes:
>
> function start (){
>    "$@" > /dev/null 2> /dev/null &
> }
>
> The difference is that this won't remove any zero-length arguments to the
> command, e.g. a '' on the command line.  That's not a typical problem with
> the sort of use you have, however.

Ok I make this modification thanks you and Frank Terbeck.