From: <tomas@tuxteam.de>
To: emacs-devel@gnu.org
Subject: Re: master 68ae6fa: Improved light/dark colour predicate (bug#41544)
Date: Fri, 12 Jun 2020 18:22:37 +0200 [thread overview]
Message-ID: <20200612162237.GA29484@tuxteam.de> (raw)
In-Reply-To: <93F81C41-E774-4C02-9E9D-5B2CD1F66445@acm.org>
[-- Attachment #1: Type: text/plain, Size: 1299 bytes --]
On Fri, Jun 12, 2020 at 05:50:32PM +0200, Mattias Engdegård wrote:
> 11 juni 2020 kl. 21.22 skrev Yuri Khan <yuri.v.khan@gmail.com>:
>
> > My equipment [...] says that shade of gold in fact
> > performs okay in all four scenarios
>
> I have no reason to doubt your observations. Let's try a plebiscite!
>
> * * *
>
> Dear Emacs developer or user,
>
> 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).
>
> Colours with luminance (last column) below the cutoff will be use white text, others black. It is mainly Emacs in graphical (non-TTY) mode that is of interest.
>
> Please reply (to emacs-devel or to me) the following pieces of information:
>
> * the cutoff value you found optimal
You mean: where the color name is most readable against all
backgrounds? 0.375 (although 0.325 gives fine results too)
> * system information: window system, screen, anything you think is relevant
X on Gnu/Linux, thinkpad X230 with the cheaper screen (no IPS)
> * whether you use a light or dark background in your Emacs
Dark Emacs (but not too dark, #333333-ish)
Cheers
-- tomás
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2020-06-12 16:22 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 [this message]
2020-06-12 18:36 ` Yuri Khan
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=20200612162237.GA29484@tuxteam.de \
--to=tomas@tuxteam.de \
--cc=emacs-devel@gnu.org \
/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).