From: Oliver Kiddle <okiddle@yahoo.co.uk>
To: zsugabubus <zsugabubus@national.shitposting.agency>,
"zsh-workers@zsh.org" <zsh-workers@zsh.org>
Subject: Re: Funky list-colors
Date: Thu, 05 Dec 2019 08:44:03 +0100 [thread overview]
Message-ID: <10717-1575531843.649205@8BHq.aUkQ.N3ux> (raw)
In-Reply-To: <CAH+w=7Y_TDFMU_uEHtEbmAUiNRLs2Ek_NdbhUU9fAzc8ZxAYww@mail.gmail.com>
Bart wrote:
> For even more detail you can use something similar to:
> compadd -o -d labels_array -a filenames_array
> where there is one entry in $labels_array for each entry in
> $filenames_array. The completion system will arrange to build a grid
> of the labels and names so that each name is paired with the
> corresponding element from the labels. However, it does place the
> labels to the right of the names rather than to the left.
Actually the array specified with -d is not just for the labels but for
the whole string - match and label. So you can make any change you
like to how the match appears in the completion listing for your
own custom version of the LIST_TYPES option.
The common rendering of the match followed by a separator (-- by
default) and a label is not part of compadd. (in terms of man
pages/documentation sections, it is part of zshcompsys rather than
zshcompwid). In most, but by no means all, cases this is done from
_describe.
This also means that for things like the list-colors style, patterns
match the whole display string. It can thus be used to change
attributes for either or both match and label. For an example, try:
'=(#b)(--) (*)==32=3'
Oliver
next prev parent reply other threads:[~2019-12-05 19:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-29 12:21 zsugabubus
2019-11-29 16:06 ` Bart Schaefer
2019-11-29 17:23 ` zsugabubus
2019-11-29 19:22 ` Bart Schaefer
2019-11-29 20:37 ` zsugabubus
2019-12-04 23:27 ` Bart Schaefer
2019-12-05 7:44 ` Oliver Kiddle [this message]
2019-12-05 11:07 ` Sebastian Gniazdowski
2019-12-05 11:19 ` Roman Perepelitsa
2019-12-05 17:40 ` Oliver Kiddle
2019-12-07 20:58 ` zsugabubus
2019-12-07 21:42 ` Oliver Kiddle
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=10717-1575531843.649205@8BHq.aUkQ.N3ux \
--to=okiddle@yahoo.co.uk \
--cc=zsh-workers@zsh.org \
--cc=zsugabubus@national.shitposting.agency \
/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).