[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: VOTE: Changing completions-common-part face's default

From: Dmitry Gutov
Subject: Re: VOTE: Changing completions-common-part face's default
Date: Thu, 7 Nov 2019 16:43:43 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0

On 07.11.2019 15:52, João Távora wrote:
On Thu, Nov 7, 2019 at 1:27 PM Yuri Khan <address@hidden <mailto:address@hidden>> wrote:

 > I thought I’d chime in with some actual color science to back the
 > feelings in this thread.

Very nice.  Thanks.

I concur. I should find the same links very useful in some future theming discussions.

 > There is no formula for calculating how distinguishable two different
 > text colors on the same background are.

I would say that the next best thing is to calculate the contrast
difference between two colors period.

blue4 vs black is 1.27
blue3 vs black is 1.87

So very good for reading the text, very bad for distinguishing
the colors in two adjacent letters.

I don't know if it works like that.

The necessary contrast between fg and bg is about being able to *read* the letter, and not just being able to notice that the color is different. So the standard for distinguishing colors should be much lower.

This points to a rule for finding the perfect good compromise:
find the color equidistant to both black and white that passes
both tests.  Of all the proposed faces so far, cyan4 seems to
come closest to passing both these bars. But I found DodgerBlue3
passes the "vs white" (4.7) bar and almost passes the "vs black"
bar (4.1).

It's a really pretty color, but if the goal is choosing a "not in-your-face" option, it fails that condition for the above reason.

(of course we could just let styles choose how it highlights completions
from a given face pool, but that's sadly off the table)

To reiterate something I said in another email: if flex stops using common-part where it does now, company-capf will become confused.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]