From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15189 invoked by alias); 19 May 2015 03:09:40 -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: 35201 Received: (qmail 6766 invoked from network); 19 May 2015 03:09:39 -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.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no version=3.4.0 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:message-id:date:in-reply-to:comments :references:to:subject:mime-version:content-type; bh=Ds50nFmpsDhHxhDzbPmQf9CgSCNyWksRWWZF6kUj2NE=; b=lddKY1NaJXG/FgEodG/E5vufL7QTUnLz5ivUxw0eY1XfELkeYJnZzpBlLHnhsTzHvh bUlCNnn4ndTZ+Th0tysbeq4Nj0E/xPEZ3idy2zYUJCbyJ9EOXkr97bZsa9FcJAfSgCTq EBY6PPNK613INkihs+liSAP5I3m7P1kPzmrlMeD0iiLAsW16eCKCLmeZY4n1QLpAeegf CRMOyEc1ghtbG9s+JaY5fj8P8IJz6Olnm9IMSav+Du4tbINn3dV1cEeCg9Rot3x64fRR LNxN339NP32uyVuP9ZzTKOzo6GIrH/yzmY+ZQFEI+MS95wrthVmf/2EGEbGxd7jjqAPP EKlQ== X-Gm-Message-State: ALoCoQkWyS+vOwPpmT5RhUhunoFIp0YJa9iPrLmJAT7ndHGQv03F8BOJZhXaDXJMZ+jr63cph/Cf X-Received: by 10.50.85.113 with SMTP id g17mr18433414igz.46.1432004972681; Mon, 18 May 2015 20:09:32 -0700 (PDT) From: Bart Schaefer Message-Id: <150518200924.ZM5101@torch.brasslantern.com> Date: Mon, 18 May 2015 20:09:24 -0700 In-Reply-To: <20150519015156.GD2024@tarsus.local2> Comments: In reply to Daniel Shahaf "Re: [PATCH] Proposed change to show-ambiguity context" (May 19, 1:51am) References: <150516223948.ZM5746@torch.brasslantern.com> <20150517234530.GH2214@tarsus.local2> <150517210336.ZM857@torch.brasslantern.com> <20150519015156.GD2024@tarsus.local2> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-workers@zsh.org Subject: Re: [PATCH] Proposed change to show-ambiguity context MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On May 19, 1:51am, Daniel Shahaf wrote: } } 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. Well, that, and also that underneath there is only one ZLS_COLORS; the zstyles for list-colors and show-ambiguity are both just other ways to set the value of ZLS_COLORS. (I typo'd LS_COLORS where I meant ZLS in my previous answer.)