From: Eli Zaretskii <eliz@gnu.org>
To: Van L <van@scratch.space>
Cc: 33093@debbugs.gnu.org
Subject: bug#33093: 26.1, 7.2 emacs-mac; M-x list-colors-display RET; L1 is black on black
Date: Sun, 21 Oct 2018 15:28:05 +0300 [thread overview]
Message-ID: <83o9bntrfu.fsf@gnu.org> (raw)
In-Reply-To: <DCECFB0E-11E2-4848-B7FD-6677B2D3C9FE@scratch.space> (message from Van L on Sun, 21 Oct 2018 16:12:29 +1100)
> From: Van L <van@scratch.space>
> Date: Sun, 21 Oct 2018 16:12:29 +1100
> Cc: 33093@debbugs.gnu.org
>
> > Each color's name is shown twice, once when the color is used as
> > background, the other time it is used as foreground. Are you saying
> > that you see neither of these two for some colors?
>
> I see three columns. As an aside, previously my background color was ‘antique white’ now it is ‘gainsboro’. Back to here. The columns according to how I interpret them:
>
> 1. text on color bar, this is the background-color, and the text is unreadable at line 1 (black on black)
> 2. the same color as foreground-color, the black text is readable on my normal background color
> 3. the RGB hex values
>
> I am saying the problem is in column one where WYSIWYG background-color and text color are identical it is unreadable.
Could be foe some combinations, but then the color name is legible in
the other column.
> I’m suggest in column one, where the black text is too close to the background-color being demonstrated, such as blue, medium blue, that the text-color in column one should be inversed to white from black.
Volunteers are welcome to submit patches to do that.
next prev parent reply other threads:[~2018-10-21 12:28 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 [this message]
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
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
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=83o9bntrfu.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=33093@debbugs.gnu.org \
--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 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).