zsh-users
 help / color / mirror / code / Atom feed
From: "Jérémie Roquet" <arkanosis@gmail.com>
To: Peter Stephenson <Peter.Stephenson@csr.com>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: Using the same completion function for various commands
Date: Mon, 6 Dec 2010 16:31:11 +0100	[thread overview]
Message-ID: <AANLkTi=M7gD0ZWTKuqt3-WhDqTzDd-_ChPWFP5ZsOKxT@mail.gmail.com> (raw)
In-Reply-To: <20101206151124.389fd287@pwslap01u.europe.root.pri>

2010/12/6 Peter Stephenson <Peter.Stephenson@csr.com>:
> On Mon, 6 Dec 2010 16:03:51 +0100
> Mikael Magnusson <mikachu@gmail.com> wrote:
>
>> 2010/12/6 Jérémie Roquet <arkanosis@gmail.com>:
>> > Hi,
>> >
>> > 2010/12/6 Mikael Magnusson <mikachu@gmail.com>:
>> >> You can also do this in your .zshrc instead of in the completer if
>> >> you wish, just write
>> >> compdef _foo -p 'foo_*'
>> >>
>> >> At least that's what the documentation says, it doesn't seem to
>> >> work that well.
>> >
>> > It works fine for me with 4.3.10, did I miss something?
>>
>> When i tried compdef _du -p foo_\*, i only got single-letter options
>> completed.
>>
>
> That means it's working perfectly.  It's hitting this line at the top of
> _du
>
>  _pick_variant gnu=Free\ Soft unix --version /dummy/no-such-file
>
> and deciding, quite reasonably in my opinion, that foo_\* is not a GNU
> variant of du.  So it's going to the other branch, where the options are
> simpler.

I'm getting some weird behaviour with some commands, though. For example :

$ aap -<tab>
--                          -- end of options, targets and assignments follow
--changed                   -- consider specified file changed
--command         -c        -- execute a command after reading the recipe
--contents        -C        -- only build when file contents changed
<snip>

$ compdef _aap bar
$ bar -<tab>
--                          -- end of options, targets and assignments follow
--changed                   -- consider specified file changed
--command         -c        -- execute a command after reading the recipe
--contents        -C        -- only build when file contents changed
<snip>

$ compdef _aap -p baz
$ baz -<tab>
zsh: do you wish to see all 1152 possibilities (1154 lines)?<y>
option
--
--changed
--command
--contents
<snip>
<space>
<space>
<snip>
-c
-C
-k
<snip>
<space>
<space>
<snip>
-- end of options, targets and assignments follow
-- consider specified file changed
-- execute a command after reading the recipe
<snip>

I guess there is something wrong in _aap, but I don't understand why
the behaviour is different with and without the -p

Best regards,

-- 
Jérémie


      parent reply	other threads:[~2010-12-06 15:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-06 14:12 Martin Richter
2010-12-06 14:54 ` Mikael Magnusson
2010-12-06 15:01   ` Jérémie Roquet
2010-12-06 15:03     ` Mikael Magnusson
2010-12-06 15:11       ` Peter Stephenson
2010-12-06 15:18         ` Mikael Magnusson
2010-12-06 16:10           ` Peter Stephenson
2010-12-06 16:21             ` Peter Stephenson
2010-12-06 16:44               ` Bart Schaefer
2010-12-06 17:08                 ` Peter Stephenson
2010-12-06 19:39           ` Oliver Kiddle
2010-12-07 11:52             ` Peter Stephenson
2010-12-06 15:23         ` Martin Richter
2010-12-06 15:31         ` Jérémie Roquet [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='AANLkTi=M7gD0ZWTKuqt3-WhDqTzDd-_ChPWFP5ZsOKxT@mail.gmail.com' \
    --to=arkanosis@gmail.com \
    --cc=Peter.Stephenson@csr.com \
    --cc=zsh-users@zsh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).