unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Yuri Khan <yuri.v.khan@gmail.com>
To: "Mattias Engdegård" <mattiase@acm.org>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
	Emacs developers <emacs-devel@gnu.org>
Subject: Re: master 68ae6fa: Improved light/dark colour predicate (bug#41544)
Date: Sat, 13 Jun 2020 01:36:30 +0700	[thread overview]
Message-ID: <CAP_d_8WiUsdUbGfCuRZ_QF0-hvBUSAmpVcPcQG77MDa5YpjzBg@mail.gmail.com> (raw)
In-Reply-To: <93F81C41-E774-4C02-9E9D-5B2CD1F66445@acm.org>

On Fri, 12 Jun 2020 at 22:50, Mattias Engdegård <mattiase@acm.org> wrote:

> Please load the attached code (any Emacs version), and run M-x contrast-compare with various cutoff values on your favourite system, to find what value is best for readability of the colour names (first column).
> Please reply (to emacs-devel or to me) the following pieces of information:
>
> * the cutoff value you found optimal
> * system information: window system, screen, anything you think is relevant
> * whether you use a light or dark background in your Emacs

Despite science calling for .18, I find that my subjective optimal
cutoff is somewhere between .25 and .31, even if I change the formulae
to more accurately model the piecewise gamma correction of sRGB:

-               (r (expt (nth 0 rgb) 2.2))
+               (R (nth 0 rgb))
+               (r (if (<= R 0.03928)
+                      (/ R 12.92)
+                    (expt (/ (+ R 0.055) 1.055) 2.4)))

(same for g and b.)

I am on GTK+3/X11, Dell P2415Q (HiDPI IPS), RGB-subpixel slight-hinted
Cousine font at 10.5pt, on overall dark gray background (#414042).



  parent reply	other threads:[~2020-06-12 18:36 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200610181238.9796.44750@vcs0.savannah.gnu.org>
     [not found] ` <20200610181239.947C4204DF@vcs0.savannah.gnu.org>
2020-06-10 19:20   ` master 68ae6fa: Improved light/dark colour predicate (bug#41544) Stefan Monnier
2020-06-10 19:34     ` Mattias Engdegård
2020-06-10 20:01       ` Stefan Monnier
2020-06-11  5:15     ` Yuri Khan
2020-06-11 16:15       ` Mattias Engdegård
2020-06-11 19:22         ` Yuri Khan
2020-06-12 15:50           ` Mattias Engdegård
2020-06-12 16:22             ` tomas
2020-06-12 18:36             ` Yuri Khan [this message]
2020-06-13 10:55               ` Mattias Engdegård
2020-06-12 19:02             ` Drew Adams
2020-06-12 19:09             ` Stephen Leake
2020-06-18 19:28               ` Mattias Engdegård
2020-06-18 19:35                 ` Drew Adams
2020-06-18 20:04                   ` Mattias Engdegård
2020-06-18 20:32                     ` Drew Adams
2020-06-21  7:51                       ` Mattias Engdegård
2020-06-18 19:40                 ` Basil L. Contovounesios
2020-06-18 19:58                   ` Mattias Engdegård
2020-06-13  4:05             ` Richard Stallman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAP_d_8WiUsdUbGfCuRZ_QF0-hvBUSAmpVcPcQG77MDa5YpjzBg@mail.gmail.com \
    --to=yuri.v.khan@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=mattiase@acm.org \
    --cc=monnier@iro.umontreal.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).