From: Juri Linkov <juri@jurta.org>
Cc: pogonyshev@gmx.net, monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: dashes and non-breaking spaces
Date: Wed, 05 Jan 2005 07:46:45 +0200 [thread overview]
Message-ID: <87brc4xwai.fsf@jurta.org> (raw)
In-Reply-To: <shzmzoncfg.fsf@tux.gnu.franken.de> (Karl Eichwalder's message of "Tue, 04 Jan 2005 21:53:39 +0100")
Karl Eichwalder <ke@gnu.franken.de> writes:
> Yes, it is useful to make these codes visible in edit modes; displaying
> it in most viewing modes like « mail » and « news readers » is
> annoying
I agree. It is useful only in editing modes. This is like highlighting
trailing whitespace which is useful only for writable files, i.e. where
whitespace deletions can be saved. There should be a user option
specifying the predicate to activate the mode, with the default value
like `buffer-read-only'.
> Using blue for the backslash is also arguable; a single slash in blue is
> hard to distinguish from the surround text in black. In the past I used
> an IndianRed underscore for the no-breaking space.
Yes, blue is one of the most unsuitable colors. It seems everyone already
agreed on the following colors for escape glyphs:
(defface escape-glyph
'((((class color) (min-colors 88) (background light))
:foreground "dark red")
(((class color) (min-colors 88) (background dark))
:foreground "tan1")
(((class color) (min-colors 8))
:foreground "red"))
"Face for characters displayed as ^-sequences or \\-sequences."
:group 'basic-faces)
If these colors are unsuitable for no-break spaces then perhaps
a better face is `trailing-whitespace', or maybe it will require
a new face.
--
Juri Linkov
http://www.jurta.org/emacs/
next prev parent reply other threads:[~2005-01-05 5:46 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 [this message]
2005-01-06 4:53 ` Richard Stallman
2005-01-12 2:02 ` Juri Linkov
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87brc4xwai.fsf@jurta.org \
--to=juri@jurta.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=pogonyshev@gmx.net \
/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.