From: Juri Linkov <juri@jurta.org>
Cc: monnier@iro.umontreal.ca, pogonyshev@gmx.net
Subject: Re: Gnus not escaping NBSP and soft-hyphen
Date: Wed, 22 Jun 2005 16:32:07 +0300 [thread overview]
Message-ID: <87oe9yh45k.fsf@jurta.org> (raw)
In-Reply-To: <qlkr7ev5o4k.fsf@clipper.ens.fr> (Gaëtan LEURENT's message of "Wed, 22 Jun 2005 00:41:31 +0200")
> Maybe a more systematic way to proceed would be to disable NBSP-escaping
> in read-only buffers (but it could sometimes be confusing, too).
Disabling NBSP highlighting in read-only buffers makes some sense.
The reason is that in read-only buffers users usually can't fix NBSP
(if it is wrong). I used such a rule for enabling show-trailing-whitespace
to show trailing whitespace only in editable buffers. But sometimes
this rule fails: some read-only buffers can be switched to edit mode,
some editable buffers are not writable. So finally I reached the rule
that sets the buffer-local show-trailing-whitespace only on files in
specified subdirectories.
This shows that show-trailing-whitespace is flexible enough to allow arbitrary
customization, but escape-glyph is not. There is a need for a buffer-local
variable similar to show-trailing-whitespace to enable/disable highlighting
of control characters and nbsp with escape-glyph face on a per-buffer basis.
--
Juri Linkov
http://www.jurta.org/emacs/
next prev parent reply other threads:[~2005-06-22 13:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-21 16:58 Gnus not escaping NBSP and soft-hyphen Gaëtan LEURENT
2005-06-21 18:38 ` Paul Pogonyshev
2005-06-21 19:21 ` Gaëtan LEURENT
2005-06-21 21:30 ` Stefan Monnier
2005-06-21 22:41 ` Gaëtan LEURENT
2005-06-22 0:14 ` Miles Bader
2005-06-22 13:32 ` Juri Linkov [this message]
2005-06-23 0:43 ` Miles Bader
2005-06-23 17:37 ` Kevin Rodgers
2005-06-24 16:37 ` Richard M. Stallman
2005-06-24 17:17 ` Kevin Rodgers
2005-06-24 19:07 ` Juri Linkov
2005-06-25 13:34 ` Richard M. Stallman
2005-06-24 19:07 ` Juri Linkov
2005-06-24 22:22 ` Miles Bader
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=87oe9yh45k.fsf@jurta.org \
--to=juri@jurta.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 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).