Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: [PATCH] Proposed change to show-ambiguity context
- X-seq: zsh-workers 35177
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxx
- Subject: Re: [PATCH] Proposed change to show-ambiguity context
- Date: Sun, 17 May 2015 21:03:36 -0700
- In-reply-to: <20150517234530.GH2214@tarsus.local2>
- List-help: <mailto:zsh-workers-help@zsh.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:zsh-workers@zsh.org>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- References: <150516223948.ZM5746@torch.brasslantern.com> <20150517234530.GH2214@tarsus.local2>
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.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author