From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-users-return-20152-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 4168 invoked by alias); 13 Apr 2015 11:01:02 -0000
Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Users List <zsh-users.zsh.org>
List-Post: <mailto:zsh-users@zsh.org>
List-Help: <mailto:zsh-users-help@zsh.org>
X-Seq: 20152
Received: (qmail 13052 invoked from network); 13 Apr 2015 11:00:59 -0000
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW
	autolearn=ham version=3.3.2
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        bh=52NKvxffhgYgmdjxXxlP5VFRJxmGNp0t5BojBhRYPP0=;
        b=Y75a/6YOkaEw28LgZyx+X2o88SDG/DpSvUKYzwW/gWgIYON8XTPJI/3N2QV8lH0CwX
         GqZH7RwvltCndi5d1dNnVOAzs4KiFenlfmk3UnWpyd4bW1kCow3yvA+TNDKLuU22syRR
         s73+3N6aPNzMdFCpl+MEa9Z0on4ka5ZMKEL7qiSz8Hn3xeyppJUkGRje1W2k2FM8Lvw1
         F/sU79Ip+CYCc88NdJhkqzHK5Gs2p6XRpOtw0KNf5lfHnMFwuk205DtAqLgvnhop72pB
         4wzU0QsjIULeb0G744R2SB90UrzWBfElByJH9pU0Wt7xWH+sS+321IQOfp6NhvksDEYU
         9qTA==
MIME-Version: 1.0
X-Received: by 10.112.204.135 with SMTP id ky7mr12845911lbc.65.1428922854000;
 Mon, 13 Apr 2015 04:00:54 -0700 (PDT)
In-Reply-To: <mgemjb$9bk$1@ger.gmane.org>
References: <mg9fo4$d3$1@ger.gmane.org>
	<E1YgyLH-00089n-0P@smtp.tt-solutions.com>
	<150411130249.ZM27498@torch.brasslantern.com>
	<552A67C4.1080903@thregr.org>
	<150412115830.ZM21859@torch.brasslantern.com>
	<mgemjb$9bk$1@ger.gmane.org>
Date: Mon, 13 Apr 2015 13:00:53 +0200
Message-ID: <CABZhJg_uryzYZ=DYMmSFgnRZg5JPiEfg-nyobDVjbW6yFrCOcA@mail.gmail.com>
Subject: Re: show-ambiguity style
From: =?UTF-8?Q?Jesper_Nyg=C3=A5rds?= <jesper.nygards@gmail.com>
To: zsh-users@zsh.org
Content-Type: multipart/alternative; boundary=001a11c3c1b81fcda705139907fb

--001a11c3c1b81fcda705139907fb
Content-Type: text/plain; charset=UTF-8

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.
>
>
>

--001a11c3c1b81fcda705139907fb--