From: Juri Linkov <juri@jurta.org>
Cc: occitan@esperanto.org, emacs-devel@gnu.org, storm@cua.dk
Subject: Re: [Emacs-trunk-diffs] Changes to emacs/lisp/faces.el
Date: Fri, 24 Dec 2004 04:28:52 +0200 [thread overview]
Message-ID: <87sm5wfhh3.fsf@jurta.org> (raw)
In-Reply-To: <E1Ceabb-0003xb-KJ@fencepost.gnu.org> (Richard Stallman's message of "Wed, 15 Dec 2004 09:58:19 -0500")
Richard Stallman <rms@gnu.org> writes:
> I think this looks better too -- but the current escape-glyph face doesn't
> stand out very much -- what about "red" foreground instead?
>
> I think it should not stand out very much.
>
> The aim isn't to help the user quickly find all the escape sequences,
> merely to confirm that they are escape sequences. For this purpose, a
> font that is merely visible is ideal. If it stands out, it tends to
> be distracting.
The current `blue' is one of the most unsuitable colors. It stand out
very much. Blue is mostly used for highlighting the important parts
of the buffer: in programming modes it highlights function names,
in Dired - file names. Using it for escape sequences makes them
too distracting.
I highly recommend `dark red' for numerous reasons:
1. It does not stand out very much, but still differs from the black
color on light backgrounds.
2. ^L page separators in the source buffers will look like red comments,
but still can be distinguished from the red since it is darker.
3. In rose strings it does not stand out too, but it's visible that
dark red is not the same as rose.
4. The red color tells the user to turn attention to potentially
dangerous codes, but a darker shade makes it not too noticeable.
The same dark red color is also suitable for dark backgrounds.
--
Juri Linkov
http://www.jurta.org/emacs/
next prev parent reply other threads:[~2004-12-24 2:28 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1CZoXW-0007hE-UW@lists.gnu.org>
[not found] ` <E1Ca4Kt-00067g-EH@fencepost.gnu.org>
2004-12-03 9:18 ` [Emacs-trunk-diffs] Changes to emacs/lisp/faces.el Kim F. Storm
2004-12-04 2:48 ` Richard Stallman
2004-12-05 17:52 ` Juri Linkov
2004-12-05 18:32 ` Daniel Pfeiffer
2004-12-06 1:40 ` Richard Stallman
2004-12-07 22:40 ` Daniel Pfeiffer
2004-12-07 23:48 ` Stefan Monnier
2004-12-08 8:47 ` Daniel Pfeiffer
2004-12-08 15:16 ` Stefan Monnier
2004-12-08 22:15 ` Richard Stallman
2004-12-08 22:15 ` Richard Stallman
2004-12-12 9:19 ` Daniel Pfeiffer
2004-12-13 9:03 ` Juri Linkov
2004-12-13 14:51 ` Stefan Monnier
2004-12-13 19:51 ` Richard Stallman
2004-12-13 23:41 ` Daniel Pfeiffer
2004-12-14 23:22 ` Richard Stallman
2004-12-17 0:54 ` Richard Stallman
2004-12-19 9:41 ` Daniel Pfeiffer
2004-12-21 11:21 ` Richard Stallman
2004-12-23 20:39 ` Daniel Pfeiffer
2004-12-14 12:32 ` Kim F. Storm
2004-12-15 10:56 ` Juri Linkov
2004-12-15 11:21 ` Kim F. Storm
2004-12-15 12:01 ` Robert J. Chassell
2004-12-15 14:58 ` Richard Stallman
2004-12-15 16:14 ` Kim F. Storm
2004-12-15 20:35 ` Daniel Pfeiffer
2004-12-24 2:28 ` Juri Linkov [this message]
2004-12-24 13:26 ` Robert J. Chassell
2004-12-26 19:42 ` Juri Linkov
2004-12-27 8:00 ` Eli Zaretskii
2004-12-27 19:53 ` Juri Linkov
2004-12-27 22:01 ` Eli Zaretskii
2004-12-27 22:56 ` Stefan Monnier
2004-12-28 17:25 ` Richard Stallman
2004-12-28 2:38 ` Juri Linkov
2004-12-28 4:47 ` Eli Zaretskii
2004-12-28 7:52 ` Juri Linkov
2004-12-28 20:36 ` Eli Zaretskii
2004-12-29 0:22 ` Juri Linkov
2004-12-29 4:45 ` Eli Zaretskii
2004-12-30 7:33 ` Juri Linkov
2004-12-30 14:21 ` Alex Schroeder
2004-12-30 16:33 ` Drew Adams
2004-12-30 20:59 ` Richard Stallman
2004-12-28 4:57 ` Richard Stallman
2004-12-25 15:12 ` 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=87sm5wfhh3.fsf@jurta.org \
--to=juri@jurta.org \
--cc=emacs-devel@gnu.org \
--cc=occitan@esperanto.org \
--cc=storm@cua.dk \
/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).