From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: Color in completions
Date: Sun, 31 Jan 2016 16:38:21 +0100 [thread overview]
Message-ID: <CAKc7PVAraFjBxoMhf=EpjPW+GnynDqCChKvzowt_g39C5Hibgg@mail.gmail.com> (raw)
In-Reply-To: <160129144546.ZM24675@torch.brasslantern.com>
On 29 January 2016 at 23:45, Bart Schaefer <schaefer@brasslantern.com> wrote:
> You can get color in completion listings with the complist module,
> see "man zshmodules" or "info zsh 'The zsh/complist Module'". In
> particular this reference to $ZLS_COLORS:
>
> The leading-equals form also allows different parts of the displayed
> strings to be colored differently. For this, the pattern has to use the
> `(#b)' globbing flag and pairs of parentheses surrounding the parts of
> the strings that are to be colored differently. ...
Managed to do this. Had to:
1. Figure out to use _wanted instead of only compadd
2. Figure out what pattern to give to zstyle:
zstyle ':completion:*:zplugin:*:argument-rest' list-colors
'=(#b)(*)/(*)==1;35=1;33'
When I display $curcontext within _zplugin (after adding -C to
_arguments), it shows: :complete:zplugin:argument-rest. I wonder why
do I need the additional ":*:" before "argument-rest" ? Or even the
first one.
https://github.com/psprint/zplugin/blob/master/_zplugin
Best regards,
Sebastian Gniazdowski
next prev parent reply other threads:[~2016-01-31 15:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-29 13:13 Sebastian Gniazdowski
2016-01-29 22:45 ` Bart Schaefer
2016-01-31 15:38 ` Sebastian Gniazdowski [this message]
2016-01-31 17:39 ` Bart Schaefer
2016-01-31 18:52 ` Sebastian Gniazdowski
2016-02-01 7:49 ` Sebastian Gniazdowski
2016-02-01 14:53 ` Bart Schaefer
2016-02-01 16:25 ` Sebastian Gniazdowski
2016-02-01 21:31 ` Bart Schaefer
2016-02-02 11:21 ` Sebastian Gniazdowski
2016-02-02 17:49 ` 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='CAKc7PVAraFjBxoMhf=EpjPW+GnynDqCChKvzowt_g39C5Hibgg@mail.gmail.com' \
--to=sgniazdowski@gmail.com \
--cc=schaefer@brasslantern.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).