From: Silvio Ricardo Cordeiro <silvioricardoc@gmail.com>
To: Daniel Shahaf <d.s@daniel.shahaf.name>
Cc: zsh-workers@zsh.org
Subject: Re: Zstyle command completion does not work for some executables
Date: Fri, 29 Jan 2016 10:35:43 -0200 [thread overview]
Message-ID: <CABq1aV8Wv6bMGoodGCOX=wGmhd6zzJxJR=AZc4eA1JYRr+x4MQ@mail.gmail.com> (raw)
In-Reply-To: <20160129091907.GC28305@tarsus.local2>
[-- Attachment #1: Type: text/plain, Size: 1277 bytes --]
For killall & rake, I get "testing" as a suggestion, as I expected. For
the others, nothing happens (they continue trying to complete with
filenames, the default behavior).
Do I have to somehow specify that "this command must obey the command
style" for my custom commands?
Thanks,
2016-01-29 7:19 GMT-02:00 Daniel Shahaf <d.s@daniel.shahaf.name>:
> Silvio Ricardo Cordeiro wrote on Thu, Jan 28, 2016 at 12:52:44 -0200:
> > On an otherwise empty .zshrc:
> >
> > Some completion specifications work normally:
> >
> > > zstyle ':completion:*:*killall*:*' command 'echo testing'
> > > zstyle ':completion:*:*rake*:*' command 'echo testing'
>
> What is happening? What do you want to happen?
>
> The 'command' style isn't used by all completion functions.
>
> Cheers,
>
> Daniel
>
> > While other completion just do *not* work:
> >
> > > zstyle ':completion:*:*bash*:*' command 'echo testing'
> > > zstyle ':completion:*:*some_file_in_PATH*:*' command 'echo testing'
> >
> > zstyle ':completion:*:*inexistent_executable*:*' command 'echo testing'
> > >
> >
> > Is there any way to debug this kind of behavior? I have tried pressing
> > "^X?", but the output is the same for "killall" and for "bash"...
> >
> > --
> > Silvio Ricardo Cordeiro
>
--
Silvio Ricardo Cordeiro
next prev parent reply other threads:[~2016-01-29 12:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 14:52 Silvio Ricardo Cordeiro
2016-01-28 14:54 ` Silvio Ricardo Cordeiro
2016-01-29 9:19 ` Daniel Shahaf
2016-01-29 12:35 ` Silvio Ricardo Cordeiro [this message]
2016-01-29 13:01 ` Peter Stephenson
2016-01-29 13:19 ` Silvio Ricardo Cordeiro
2016-01-29 17:52 ` Bart Schaefer
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='CABq1aV8Wv6bMGoodGCOX=wGmhd6zzJxJR=AZc4eA1JYRr+x4MQ@mail.gmail.com' \
--to=silvioricardoc@gmail.com \
--cc=d.s@daniel.shahaf.name \
--cc=zsh-workers@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).