zsh-users
 help / color / mirror / code / Atom feed
From: "Jesper Nygårds" <jesper.nygards@gmail.com>
To: zsh-users@zsh.org
Subject: Re: show-ambiguity style
Date: Mon, 13 Apr 2015 13:00:53 +0200	[thread overview]
Message-ID: <CABZhJg_uryzYZ=DYMmSFgnRZg5JPiEfg-nyobDVjbW6yFrCOcA@mail.gmail.com> (raw)
In-Reply-To: <mgemjb$9bk$1@ger.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 1180 bytes --]

This is interesting. I had also missed it.

I ran into something that perhaps is impossible to solve. If I use the
following:

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.

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?



On Sun, Apr 12, 2015 at 11:03 PM, Yuri D'Elia <wavexx@thregr.org> wrote:

> On 04/12/2015 08:58 PM, Bart Schaefer wrote:
> > I don't know that it makes any difference to efficiency, but to have
> > the ambiguity disply overlaid on top of the other coloring would require
> > changes to the complist internals.
>
> My guess would be that it would probably end up being simpler and more
> robust compared to the current approach.
>
> Although I won't have time to look at this anytime soon.
> Any takers?
>
> > The main thing this is telling me is that we need more examples of how
> > to set list-colors.
>
> I'll put up some examples later next week.
>
>
>

  reply	other threads:[~2015-04-13 11:01 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 [this message]
2015-04-13 15:25             ` Bart Schaefer
2015-04-13 19:20               ` Jesper Nygårds
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='CABZhJg_uryzYZ=DYMmSFgnRZg5JPiEfg-nyobDVjbW6yFrCOcA@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).