Re: [PATCH] Proposed change to show-ambiguity context

[Daniel Shahaf <d.s@daniel.shahaf.name>]

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.