From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5788 invoked by alias); 19 May 2015 01:52:01 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 35200 Received: (qmail 11083 invoked from network); 19 May 2015 01:52:00 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) 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,RCVD_IN_DNSWL_LOW,RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no version=3.4.0 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= daniel.shahaf.name; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=HwmO8THNYc8vN7NvQto9AoBTv+Q=; b=MMmZ0S Po573ObEE4qXzchJ30RDYe0z1hx5nDfH3j5xcZ0PF5ah5XP7mE1Privr3qerlXpn 7ei4r3K8LFu5lKnCBciqeaS+kLNVuuzxq/EHphJ2yYPQgoTW6ZDT3R4dE4OBc9gI tiSZkgAR7kVc/dlCLltf4t+VuVAvUj12SnDVM= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=smtpout; bh=HwmO8THNYc8vN7NvQto9AoBTv+Q=; b=WfTs4 2iUWw8xruwqZqoaCdgtvKXTdBrpfietijig3vAf2VYbtyrTVHIZ9yQoM1cwBQKDC wEnFmhQQBm8EABKtSbqXatmbIrCQ8dVvZaeSb1ulV6Ew3v+ifBbWFBROx1HuN1rJ O0b/C1wXtWkA1YuKkYy/WfHdnStudj086/JV7M= X-Sasl-enc: ur0B9pkXiJrYoCI6yAnQNCwfFEibJpp073TdmerAjyuh 1432000318 Date: Tue, 19 May 2015 01:51:56 +0000 From: Daniel Shahaf To: zsh-workers@zsh.org Subject: Re: [PATCH] Proposed change to show-ambiguity context Message-ID: <20150519015156.GD2024@tarsus.local2> References: <150516223948.ZM5746@torch.brasslantern.com> <20150517234530.GH2214@tarsus.local2> <150517210336.ZM857@torch.brasslantern.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <150517210336.ZM857@torch.brasslantern.com> User-Agent: Mutt/1.5.21 (2010-09-15) Bart Schaefer wrote on Sun, May 17, 2015 at 21:03:36 -0700: > On May 17, 11:45pm, Daniel Shahaf wrote: > } > } I always wondered list-colors and LS_COLORS were either/or, rather than > } overlay list-colors on top of LS_COLORS - that is: have the already-typed > } part of the filename in color X, the next-letter-to-be-typed in color Y, > } and the remainder of the filename colored according to LS_COLORS. (where > } X and Y are specified by list-colors/show-ambiguity) > > Because list-colors and show-ambiguity, like most of the "menu" styles, > are just alternate interfaces to the base functionality from complist. as > implemented by LS_COLORS, et al. > So you're saying, it's this way because down in ZLS_COLORS, the "pattern matching" form is filetype-agnostic and has precedence over the "per-filetype" form. Thanks for the pointer. P.S. As to your actual question in this thread, I have no opinion, as I don't use show-ambiguity, but list-colors directly, and AIUI the patch doesn't change the semantics of list-colors.