From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-users-return-20156-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 9890 invoked by alias); 13 Apr 2015 19:20:31 -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: 20156
Received: (qmail 22328 invoked from network); 13 Apr 2015 19:20:19 -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=q+9rF5wsRUse1oqFuqzS71VjN1/lVCLuRdcxKKb32LM=;
        b=GE0x9YlbaOHCEOUdrKSQoORTkNtuWAYREopzP2VcqZahUMoXH6hOVvVVFQwdSAWDIP
         foCPGRKDs+W3uJ+L6BWh7jC2/6VvgjErLexDrcWf+b8R3KslRo/YGEWN0XHqhVWYKYkM
         iX0twE2Va6OgckElk12ie+LEm3p0ELhkYZK/xTbknffCU7FKUbF14xzj0kJ1KFkCJvri
         w/k68N9iH7HuQbAq+i77N3VPM4rPPuJeLJlZli9yEdSn6Eo0LvxvxJUdVAgJ66+dNVNB
         Z0KXbrbE+RhG4TC3FKBHNV+ANAcZ4r73Wzs9M3LpuXWTuGdB2trez3b/K7LYXDvrg6op
         L7Qg==
MIME-Version: 1.0
X-Received: by 10.152.87.204 with SMTP id ba12mr14978062lab.35.1428952812934;
 Mon, 13 Apr 2015 12:20:12 -0700 (PDT)
In-Reply-To: <150413082521.ZM23777@torch.brasslantern.com>
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>
	<CABZhJg_uryzYZ=DYMmSFgnRZg5JPiEfg-nyobDVjbW6yFrCOcA@mail.gmail.com>
	<150413082521.ZM23777@torch.brasslantern.com>
Date: Mon, 13 Apr 2015 21:20:12 +0200
Message-ID: <CABZhJg8-U7eaoU3O=xizHZ5a2BKSHA0MCc-Sgjwh3-07Ev=qTw@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=001a11c364a6d0d9590513a00098

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

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.

--001a11c364a6d0d9590513a00098--