From: "Jesper Nygårds" <jesper.nygards@gmail.com>
To: zsh-users@zsh.org
Subject: Re: show-ambiguity style
Date: Mon, 13 Apr 2015 21:20:12 +0200 [thread overview]
Message-ID: <CABZhJg8-U7eaoU3O=xizHZ5a2BKSHA0MCc-Sgjwh3-07Ev=qTw@mail.gmail.com> (raw)
In-Reply-To: <150413082521.ZM23777@torch.brasslantern.com>
[-- Attachment #1: Type: text/plain, Size: 1190 bytes --]
On Mon, Apr 13, 2015 at 5:25 PM, Bart Schaefer <schaefer@brasslantern.com>
wrote:
> On Apr 13, 1:00pm, Jesper Nygards wrote:
> }
> } zstyle ':completion:*' list-colors ${(s.:.)LS_COLORS}
> } zstyle ':completion:*' show-ambiguity $color[bg-red]
> }
> } I only get EITHER the file type coloring or the ambiguity indication,
> } depending on the order of those two lines.
>
> It shouldn't depend on the order of the lines. I think if you look more
> closely, you'll find that you get show-ambiguity any time there *is* an
> ambiguity, and list-colors the rest of the time.
>
> I see. Bad testing on my part.
> } In an ideal world, I would like to have the file type coloring, AND then
> } something that indicates where the ambiguity starts, but this is perhaps
> } not possible to achieve?
>
> It's not currently possible because show-ambiguity is a trick done in
> shell script code that sits on top of list-colors which is done in the
> underlying C code.
>
> There's a bit of side discussion on zsh-workers about this right now, but
> nobody immediately available to make changes to the zsh/complist module.
>
OK. Too bad. Both are really nice, but I guess I'll have to choose then.
next prev parent reply other threads:[~2015-04-13 19:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-10 21:36 Yuri D'Elia
2015-04-11 2:21 ` lilydjwg
2015-04-11 16:33 ` Vadim Zeitlin
2015-04-11 20:02 ` Bart Schaefer
2015-04-12 12:40 ` Yuri D'Elia
2015-04-12 18:58 ` Bart Schaefer
2015-04-12 21:03 ` Yuri D'Elia
2015-04-13 11:00 ` Jesper Nygårds
2015-04-13 15:25 ` Bart Schaefer
2015-04-13 19:20 ` Jesper Nygårds [this message]
2015-04-12 12:40 ` Yuri D'Elia
2015-04-13 20:57 ` Daniel Shahaf
2015-04-13 20:21 ` zzapper
2015-04-15 19:56 ` Yuri D'Elia
2015-04-20 21:51 ` zzapper
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='CABZhJg8-U7eaoU3O=xizHZ5a2BKSHA0MCc-Sgjwh3-07Ev=qTw@mail.gmail.com' \
--to=jesper.nygards@gmail.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).