all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Van L <van@scratch.space>
Cc: 33093@debbugs.gnu.org, juri@linkov.net
Subject: bug#33093: 26.1, 7.2 emacs-mac; M-x list-colors-display RET; L1 is black on black
Date: Fri, 26 Oct 2018 09:34:27 +0300	[thread overview]
Message-ID: <83y3alp66k.fsf@gnu.org> (raw)
In-Reply-To: <835CCBC3-A66A-4830-8663-8678C59E95A3@scratch.space> (message from Van L on Fri, 26 Oct 2018 09:02:48 +1100)

> From: Van L <van@scratch.space>
> Date: Fri, 26 Oct 2018 09:02:48 +1100
> Cc: 33093@debbugs.gnu.org
> 
> It might be not worth the effort because it is near impossible to do, but to imagine whiteclouds/bluesky, you could have the text always legible where fore/background colors are too near for contrast and a swatch-like solid cursor rectangle occupying the first position of the line represents the actual foreground color. There you see the fore/background colors are in fact indistinguishable. Just a wild idea.

You mean, you think Emacs should change the foreground color without
user's say-so, just because the contrast against the background is
low?  That might be optional behavior, but certainly not the default.

(We do have infrastructure in place to test whether contrast between
background and foreground colors is low.)





  reply	other threads:[~2018-10-26  6:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-19 10:55 bug#33093: 26.1, 7.2 emacs-mac; M-x list-colors-display RET; L1 is black on black Van L
2018-10-19 12:33 ` Eli Zaretskii
2018-10-21  5:12   ` Van L
2018-10-21 12:28     ` Eli Zaretskii
2018-10-23 20:30     ` Juri Linkov
2018-10-25 13:32       ` Van L
2018-10-25 19:00         ` Juri Linkov
2018-10-25 22:02           ` Van L
2018-10-26  6:34             ` Eli Zaretskii [this message]
2018-10-28  1:46               ` Van L

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

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

  git send-email \
    --in-reply-to=83y3alp66k.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=33093@debbugs.gnu.org \
    --cc=juri@linkov.net \
    --cc=van@scratch.space \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.