From: "Drew Adams" <drew.adams@oracle.com>
To: "'David De La Harpe Golden'" <david@harpegolden.net>
Cc: 'Lars Magne Ingebrigtsen' <larsi@gnus.org>, 6693@debbugs.gnu.org
Subject: bug#6693: 24.0.50; font-lock-(builtin|doc) faces are *way* too close
Date: Sun, 3 Jul 2011 22:02:40 -0700 [thread overview]
Message-ID: <497D3295AEF04C44B010A9DEF6596B31@us.oracle.com> (raw)
In-Reply-To: <4E110EB6.3060407@harpegolden.net>
[-- Attachment #1: Type: text/plain, Size: 773 bytes --]
> font-lock-doc (#8b2252 or so) definitely still
> looks pretty different to font-lock-builtin (#7a378b or so) on my
> system.
See attached. I'd say that three of the faces shown are quite close in
appearance:
`font-lock-builtin-face' (":type", ":group")
`font-lock-doc-face' (the doc strings)
`font-lock-keyword-face' ("defcustom")
But especially the first two of these are close.
The point was also that previously these faces were better distinguished -
`font-lock-builtin-face' was `Orchid', not `MediumOrchid4'.
> Are the colors actually used on your system even
> coming out as similar hex values to those?
Those same hex values are used on my system. Those are the hex values
corresponding to the two named colors used: VioletRed4 and MediumOrchid4.
[-- Attachment #2: throw-emacs-default-colors-too-close.gif --]
[-- Type: image/gif, Size: 8776 bytes --]
next prev parent reply other threads:[~2011-07-04 5:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-21 17:32 bug#6693: 24.0.50; font-lock-(builtin|doc) faces are *way* too close Drew Adams
2011-07-03 13:06 ` Lars Magne Ingebrigtsen
2011-07-03 13:58 ` Drew Adams
2011-07-03 14:05 ` Lars Magne Ingebrigtsen
2011-07-03 14:34 ` Drew Adams
2011-07-03 14:46 ` Lars Magne Ingebrigtsen
2011-07-03 15:09 ` Drew Adams
2011-07-04 0:52 ` David De La Harpe Golden
2011-07-04 2:32 ` Chong Yidong
2011-07-04 5:15 ` Drew Adams
2011-07-04 5:27 ` Chong Yidong
2011-07-04 5:02 ` Drew Adams [this message]
2011-07-04 10:04 ` David De La Harpe Golden
2011-07-04 16:12 ` Drew Adams
2011-07-04 17:01 ` Stefan Monnier
2011-07-05 14:24 ` Lars Magne Ingebrigtsen
2011-07-05 15:24 ` Chong Yidong
2011-07-05 15:29 ` Lars Magne Ingebrigtsen
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=497D3295AEF04C44B010A9DEF6596B31@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=6693@debbugs.gnu.org \
--cc=david@harpegolden.net \
--cc=larsi@gnus.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).