zsh-workers
 help / color / mirror / code / Atom feed
From: Silvio Ricardo Cordeiro <silvioricardoc@gmail.com>
To: Peter Stephenson <p.stephenson@samsung.com>
Cc: zsh-workers@zsh.org
Subject: Re: Zstyle command completion does not work for some executables
Date: Fri, 29 Jan 2016 11:19:12 -0200	[thread overview]
Message-ID: <CABq1aV-VT-jJUOdfTD7K6jdSzAqaE1A6DJr1p_Xf2vc9T9MasA@mail.gmail.com> (raw)
In-Reply-To: <20160129130120.04e4cf11@pwslap01u.europe.root.pri>

[-- Attachment #1: Type: text/plain, Size: 1644 bytes --]

OK, thank you for the pointers.

Cheers,

2016-01-29 11:01 GMT-02:00 Peter Stephenson <p.stephenson@samsung.com>:

> On Fri, 29 Jan 2016 10:35:43 -0200
> Silvio Ricardo Cordeiro <silvioricardoc@gmail.com> wrote:
> > 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).
>
> You're missing the point of the "command" style.  Read the docmentation
> in Standard Styles in zshcompsys in more detail.  As a summary:
>
> For some commands, as part of the way the completion system gathers
> information to complete, it needs to run the command named.  In the case
> of killall and rake, it does so to find out what processes killall knows
> about or what targets rake knows about.  So if you tell it to run a
> different command here it will do so.
>
> For the vast majority of completion contexts, it doesn't need to do
> this.  It makes up the completion based on what it's been told the
> context is.  It doesn't run an external command for this.
>
> I think what you're trying to do is add completion for a new context (a
> specific command) or modify an existing one.  The "command" style has
> got nothing at all to do with this.  Instead, you need to start much
> deeper in the documentation and learn about how to add new completions
> or modify exsting ones.
>
> Oliver's chapters in the book, www.bash2zsh.com, are a good starting
> point.
>
> Otherwise, have a glance through
>
> http://zsh.sourceforge.net/Guide/zshguide06.html#l144
>
> and in particular section 6.9.
>
> pws
>



-- 
Silvio Ricardo Cordeiro

  reply	other threads:[~2016-01-29 13:19 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
2016-01-29 13:01     ` Peter Stephenson
2016-01-29 13:19       ` Silvio Ricardo Cordeiro [this message]
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=CABq1aV-VT-jJUOdfTD7K6jdSzAqaE1A6DJr1p_Xf2vc9T9MasA@mail.gmail.com \
    --to=silvioricardoc@gmail.com \
    --cc=p.stephenson@samsung.com \
    --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).