From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29166 invoked by alias); 18 May 2015 04:03:42 -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: 35177 Received: (qmail 14148 invoked from network); 18 May 2015 04:03:40 -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_H2 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=YiGhTh9hNXkjcdw3duh1As6ok+4dKWjo81vQT/Mjc7c=; b=Y8UHrnyKbruFc69MYnjvyKUgNeAyz5AE13zBr0qAwg6ko5pRb9TqQo3qXp7WV5QtzG JKIDrQVccIL0mbiafrR6s7SkHBtpPcMazxb9aijQgsmYVeet31rQ12FkV0XnPxPoGVuB fyzwKhL5BdP+lIha79VRh5fzjuBAROpQ83lB8IA02Mof5n3q6i2AeLItLKnnKpIITTkc Cb7vKpI6W4nLaLj7tGMROm+04vYH9QkQ2u2L4wH0g29SNkk177A7ZrajVOGB7xwiQ6l3 0cEOgQLzrYCLy0l+moyF/5k8kV03HmZSFHRSZyvzR+PdIKgoENLXBOAQOkD5BcNQdJQA Lyiw== X-Gm-Message-State: ALoCoQkXBrVoV+OdODAzMjZtBNePXzuxyL5ajkTyKfa65KflZYh/SKx/PpzT4bjfU5XVn/hnSeDz X-Received: by 10.202.190.134 with SMTP id o128mr17198678oif.111.1431921818973; Sun, 17 May 2015 21:03:38 -0700 (PDT) From: Bart Schaefer Message-Id: <150517210336.ZM857@torch.brasslantern.com> Date: Sun, 17 May 2015 21:03:36 -0700 In-Reply-To: <20150517234530.GH2214@tarsus.local2> Comments: In reply to Daniel Shahaf "Re: [PATCH] Proposed change to show-ambiguity context" (May 17, 11:45pm) References: <150516223948.ZM5746@torch.brasslantern.com> <20150517234530.GH2214@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 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. The zstyle mechanism is not interpreted anywhere internally, it's just a different namespace for storing things and looking them up.