From: Juri Linkov <juri@jurta.org>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: dashes and non-breaking spaces
Date: Wed, 12 Jan 2005 04:02:23 +0200 [thread overview]
Message-ID: <87u0pntjps.fsf@jurta.org> (raw)
In-Reply-To: <E1CmPee-0006Zu-R1@fencepost.gnu.org> (Richard Stallman's message of "Wed, 05 Jan 2005 23:53:48 -0500")
Richard Stallman <rms@gnu.org> writes:
> Yes, blue is one of the most unsuitable colors. It seems everyone already
> agreed on the following colors for escape glyphs:
>
> When did we even discuss them?
Below is your message on this subject. And it seems everyone agreed
on new colors (with the exception of 8-color terminals colors).
From: Richard Stallman <rms@gnu.org>
Subject: Re: [Emacs-trunk-diffs] Changes to emacs/lisp/faces.el
To: Juri Linkov <juri@jurta.org>
Cc: storm@cua.dk, occitan@esperanto.org, emacs-devel@gnu.org
Date: Sat, 25 Dec 2004 10:12:48 -0500
Reply-To: rms@gnu.org
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:
If people generally agree with you, I'll change it.
next prev parent reply other threads:[~2005-01-12 2:02 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-28 13:21 dashes and non-breaking spaces Paul Pogonyshev
2004-12-29 21:08 ` Stefan Monnier
2005-01-02 15:24 ` Paul Pogonyshev
2005-01-04 20:53 ` Karl Eichwalder
2005-01-05 5:46 ` Juri Linkov
2005-01-06 4:53 ` Richard Stallman
2005-01-12 2:02 ` Juri Linkov [this message]
2005-01-12 4:41 ` Miles Bader
2005-01-12 6:39 ` Karl Eichwalder
2005-01-12 20:58 ` Miles Bader
2005-01-12 21:58 ` Stefan Monnier
2005-01-12 22:07 ` Miles Bader
2005-01-12 22:30 ` Stefan Monnier
2005-01-13 9:29 ` David Kastrup
2005-01-13 10:37 ` Miles Bader
2005-01-14 11:33 ` Richard Stallman
2005-01-13 20:29 ` Richard Stallman
2005-01-13 21:11 ` Karl Eichwalder
2005-01-13 21:24 ` Stefan Monnier
2005-01-13 21:59 ` Karl Eichwalder
2005-01-15 0:12 ` Richard Stallman
2005-01-15 6:47 ` Karl Eichwalder
2005-01-15 14:05 ` Benjamin Riefenstahl
2005-01-15 15:36 ` Karl Eichwalder
2005-01-15 17:30 ` Benjamin Riefenstahl
2005-01-13 21:39 ` Paul Pogonyshev
2005-01-15 0:12 ` Richard Stallman
2005-01-07 13:59 ` Kim F. Storm
2005-01-07 23:04 ` Richard Stallman
2005-01-09 2:17 ` Kim F. Storm
2005-01-03 4:31 ` 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=87u0pntjps.fsf@jurta.org \
--to=juri@jurta.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).