From: Richard Stallman <rms@gnu.org>
Cc: bug-gnu-emacs@gnu.org, jidanni@jidanni.org, handa@m17n.org
Subject: Re: whitespace includes U+3000
Date: Wed, 28 Jun 2006 13:25:00 -0400 [thread overview]
Message-ID: <E1Fvdme-00060m-A2@fencepost.gnu.org> (raw)
In-Reply-To: <E1FvC36-0004bS-00@etlken> (message from Kenichi Handa on Tue, 27 Jun 2006 20:48:08 +0900)
> No. The current Emacs treat only TAB and SPACE as
> "whitespace" characters.
> It would be very easy to fix this by setting the syntax table entries
> for those characters--if there are not too many of them. So why not
> fix it?
Are you sure that "whitespace" of syntax has the same
meaning as the "whitespace" of show-trailing-whitespace?
I am not sure which one we're talking about here.
Is it show-trailing-whitespace?
If so, that would also be easy to change, if it ought to be changed.
For instance, currently ^L (formfeed) has syntax
"whitespace". But, it is displayed with glyph "^L". Should
it be the target of show-trailing-whitespace?
No.
For instance, currently NBSP (U+00A0) has syntax "."
(punctuation), and it is displayed with special face to
indicated the existing of that character. Should it be
changed to "whitespace" syntax, or shoudn't be changed?
The special face for that character should not be overridden, but the
other whitespace after it _and before it_ should probably be displayed
specially by show-trailing-whitespace.
You can probably get this result by putting NBSP into the pattern
for show-trailing-whitespace to recognize. Redisplay will override
the face, for the NBSP.
next prev parent reply other threads:[~2006-06-28 17:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-25 2:11 whitespace includes U+3000 Dan Jacobson
2006-06-26 1:00 ` Kenichi Handa
2006-06-27 10:34 ` Richard Stallman
2006-06-27 11:48 ` Kenichi Handa
2006-06-28 17:25 ` Richard Stallman [this message]
2006-06-29 2:01 ` Kenichi Handa
2006-06-29 17:57 ` Richard Stallman
2006-07-05 17:33 ` Kevin Rodgers
2006-07-07 4:13 ` 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=E1Fvdme-00060m-A2@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=bug-gnu-emacs@gnu.org \
--cc=handa@m17n.org \
--cc=jidanni@jidanni.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 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.