From: Chong Yidong <cyd@stupidchicken.com>
To: "Drew Adams" <drew.adams@oracle.com>
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: Mon, 04 Jul 2011 01:27:14 -0400 [thread overview]
Message-ID: <yyxy60ehaz1.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <74221634EBB8403589F38AE4BDAE42F8@us.oracle.com> (Drew Adams's message of "Sun, 3 Jul 2011 22:15:17 -0700")
"Drew Adams" <drew.adams@oracle.com> writes:
> I mainly see font-lock with Emacs-Lisp code (in my use), and ther is
> nothing similar to midnight blue there. On the other hand, midnight
> blue is not too different from black (the default foreground).
It is maybe a bit too dark. So maybe something like royal blue is
preferable.
> Note that (at least in Emacs-Lisp code) this face is used for coloring
> only keywords: `:type', `:group' etc. It is not for coloring large
> spans of text that someone needs to read.
There is no guarantee that this is always true, particularly since many
faces inherit from font lock faces. So it is important for all the font
lock faces to be easily distinguished from the background.
next prev parent reply other threads:[~2011-07-04 5:27 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 [this message]
2011-07-04 5:02 ` Drew Adams
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=yyxy60ehaz1.fsf@fencepost.gnu.org \
--to=cyd@stupidchicken.com \
--cc=6693@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--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 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.