From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh Users <zsh-users@zsh.org>
Subject: Re: Color in completions
Date: Mon, 1 Feb 2016 13:31:04 -0800 [thread overview]
Message-ID: <160201133104.ZM30504@torch.brasslantern.com> (raw)
In-Reply-To: <CAKc7PVCYiN17Jjpqs-MwapKfbk86qaFsnMfka_5wUYNLHwibKw@mail.gmail.com>
On Feb 1, 5:25pm, Sebastian Gniazdowski wrote:
} Subject: Re: Color in completions
}
} On 1 February 2016 at 15:53, Bart Schaefer <schaefer@brasslantern.com> wrote:
} > On Feb 1, 8:49am, Sebastian Gniazdowski wrote:
} > }
} > } tags in context :completion::complete:zplugin::
} > } argument-1 (_arguments _zplugin)
} > } commands (_describe _zplugin)
Hmm, I get (after editing _zplugin to add -C):
burner% zplg
tags in context :completion::complete:zplg::
argument-1 (_arguments _zplugin)
tags in context :completion::complete:zplg:argument-1:
commands (_zplugin)
burner% zplg unload
tags in context :completion::complete:zplg::
argument-rest (_arguments _zplugin)
tags in context :completion::complete:zplg:argument-rest:
plugins (_zplugin)
What's different about the _zplugin you're using from the one in github?
I'd forgotten that argument-N and argument-rest can appear in both the
ARGUMENT position and TAG position in the standard completion context.
Also if you look through the _complete_debug output, the context used
is really :completion::complete:zplg:argument-rest:argument-rest so
you need something in the ARGUMENT. I wonder why _complete_help gets
that wrong, but that's why both :argument-rest:* and :*:argument-rest
work.
} > zstyle ':completion:*:zplugin:*' list-colors ...
}
} I already had (#mark):
} zstyle ':completion:*:zplugin:*:argument-rest' list-colors
} '=(#b)(*)/(*)==1;35=1;33'
}
} Comparing that to your proposition:
} zstyle ':completion:*:zplugin:*' list-colors ...
} zstyle ':completion:*:zplugin:*:argument-rest' list-colors ...
}
} it seems that the zstyle #mark is correct, it just matches more - also
} the "argument-rest", which is expected, because plugin names may
} appear after a command
Your #mark style is more specific than my suggestion. That means it
matches neither the argument-1 tag nor the command and plugins tags.
next prev parent reply other threads:[~2016-02-01 21:30 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
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 [this message]
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=160201133104.ZM30504@torch.brasslantern.com \
--to=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).