From: Miles Bader <snogglethorpe@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: non-break-space in tutorial
Date: Tue, 7 Jun 2005 09:17:45 +0900 [thread overview]
Message-ID: <fc339e4a050606171760c30bdf@mail.gmail.com> (raw)
In-Reply-To: <87mzq3r70q.fsf@jurta.org>
On 6/6/05, Juri Linkov <juri@jurta.org> wrote:
> After a testing period (say, 1 week) I could remove the variable
> `show-non-break'. There seems to be no need for this variable since
> highlighting can be disabled by inheriting `no-break-space' face
> from the default face.
No. This is wrong for several reasons
1) Faces are global, but it's extremely desirable to disable special
treatment of NBSP (etc) on a per-buffer basis. So we can't get rid of
`show-nonbreak-escape'.
2) The original treatment of NBSP -- displaying it like a normal
escape character, with backslash prefix and in the normal escape
character face -- is IMO better than your method, so _at the least_ it
should be user selectable, but it seems that your patch makes this
impossible. [And I personally think it should be the default.]
3) Your patch treats "soft hyphens" in the same way as NBSP, and I'm
not sure this is desirable; it at least seems worthy of discussion.
Furthermore, we're supposed to be in some sort of pre-release state,
so please don't just install changes you _know_ to be controversial
without at least mentioning what you're going to do on the mailing
list first
BTW, something funny I noticed while testing, though I'm not sure
whether it is caused by your patch or not, is that when displaying on
a tty with `terminal-coding-system' set to nil, both NBSP and
soft-hyphen are show as "?". Since most fonts simply display these
character in the same way as their non-special brothers, wouldn't be
good for emacs to do the translation itself so that they show up ok on
simple ascii terminals?
-Miles
--
Do not taunt Happy Fun Ball.
next prev parent reply other threads:[~2005-06-07 0:17 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-26 23:19 non-break-space in tutorial Stefan Monnier
2005-05-27 11:57 ` Juri Linkov
2005-05-27 13:07 ` Paul Pogonyshev
2005-05-28 11:53 ` Richard Stallman
2005-05-29 16:08 ` Juri Linkov
2005-05-29 17:40 ` Eli Zaretskii
2005-05-30 8:48 ` Juri Linkov
2005-05-30 16:08 ` Eli Zaretskii
2005-05-31 4:18 ` Richard Stallman
2005-05-31 5:17 ` Miles Bader
2005-05-31 8:56 ` Kim F. Storm
2005-05-31 17:47 ` Richard Stallman
2005-06-06 12:52 ` Juri Linkov
2005-06-06 14:07 ` Stefan Monnier
2005-06-07 0:17 ` Miles Bader [this message]
2005-06-07 15:33 ` Juri Linkov
2005-06-07 17:12 ` Daniel Brockman
2005-06-08 0:59 ` Juri Linkov
2005-06-08 2:22 ` Henrik Enberg
2005-06-07 22:31 ` Miles Bader
2005-06-07 23:12 ` Gaëtan LEURENT
2005-06-07 23:53 ` Miles Bader
2005-06-08 0:01 ` Luc Teirlinck
2005-06-08 0:17 ` Miles Bader
2005-06-08 23:29 ` Gaëtan LEURENT
2005-06-08 23:57 ` Juri Linkov
2005-06-07 23:52 ` Juri Linkov
2005-06-08 0:17 ` Miles Bader
2005-06-08 0:57 ` Juri Linkov
2005-06-08 2:37 ` Miles Bader
2005-06-08 8:35 ` Kim F. Storm
2005-06-08 8:53 ` Miles Bader
2005-06-08 16:05 ` Stefan Monnier
2005-06-08 20:47 ` Juri Linkov
2005-06-08 21:25 ` Kim F. Storm
2005-06-08 22:53 ` Stefan Monnier
2005-06-09 14:40 ` Richard Stallman
2005-06-09 15:29 ` David Kastrup
2005-06-09 16:44 ` Juanma Barranquero
2005-05-28 11:53 ` 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=fc339e4a050606171760c30bdf@mail.gmail.com \
--to=snogglethorpe@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=miles@gnu.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 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).