zsh-users
 help / color / mirror / code / Atom feed
From: "Clemens Schüller" <cs.mlists+zsh-users@mailbox.org>
To: "Vadim A. Misbakh-Soloviov" <mva@mva.name>
Cc: zsh-users@zsh.org
Subject: Re: no tab completion with equo
Date: Thu, 09 Oct 2014 04:43:54 +0200	[thread overview]
Message-ID: <87lhoqgdxx.fsf@cougar.home.aneadesign.com> (raw)
In-Reply-To: <2438355.lmOzyVPZOc@note> (Vadim A. Misbakh-Soloviov's message of "Wed, 17 Sep 2014 13:27:22 +0700")

Hello!

"Vadim A. Misbakh-Soloviov" <mva@mva.name> writes:


> (sorry, previous try was sent to you personally, but not to the list)
> (it's strange, that client hassuch reaction on your letters to the list).
> (anyway, resentit to the list)

No problem ;-)


[ ... ]

> Also, as far as I looked in the equo and Entropy  code, --bashcomp should not 
> have it's current behaviour of returning first-level arguments all the time, 
> but should return proper arguments for each level. Unfortunately, it is 
> broken, and probably, you (and me, lol) should poke Fabio (lxnay) about that 
> on sabayon BZ or #sabayon-dev @ FreeNode.
>
> Alternativelly, it is possible to just make completion with manually 
> predefined arguments list (like I did for emerge in gentoo's zsh-completion 
> package) and call equo only when it is really needed (packages completion and 
> so on).
>
> Anyway, it needs a bit more work, than just fix tr :)

As I wrote in the other mail (reply to Barts Posting): I am not familiar
with shell coding. I will wait, until you have the time to fix the
error(s) in the _equo file.


TIA
-- 
Best Regards, Clemens Schüller


      reply	other threads:[~2014-10-09  2:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-15 18:13 Clemens Schüller
2014-09-16 13:01 ` Vadim A. Misbakh-Soloviov
2014-09-16 16:22   ` Clemens Schüller
2014-09-17  0:28     ` Bart Schaefer
2014-10-09  2:40       ` Clemens Schüller
2014-09-17  6:27     ` Vadim A. Misbakh-Soloviov
2014-10-09  2:43       ` Clemens Schüller [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=87lhoqgdxx.fsf@cougar.home.aneadesign.com \
    --to=cs.mlists+zsh-users@mailbox.org \
    --cc=cs.mlists@mailbox.org \
    --cc=mva@mva.name \
    --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).