From: Richard Stallman <rms@gnu.org>
Cc: jidanni@jidanni.org, handa@m17n.org, emacs-devel@gnu.org
Subject: Re: whitespace includes U+3000
Date: Thu, 29 Jun 2006 13:57:34 -0400 [thread overview]
Message-ID: <E1Fw0li-00023u-6T@fencepost.gnu.org> (raw)
In-Reply-To: <E1FvlqF-0007yZ-00@etlken> (message from Kenichi Handa on Thu, 29 Jun 2006 11:01:15 +0900)
Then we have different meanings in "whitespace"; the set of
characters that have "whitespace" syntax is different from
the set of characters that are displayed by "whitespace"
glyph.
That's right. There is "characters that would print as whitespace"
and there is "characters that would display as whitespace in Emacs."
These are different for good reason; it is not a mistake that they
are different.
Maybe we need to clarify the documentation so that people will
understand that there are two different concepts of whitespace.
In theory we might want to use two different words for these concepts.
But that seems strained and difficult. They really are two applications
of of the standard concept of "whitespace". We might want to speak of
"screen whitespace" and "text whitespace".
And, we can't use "whitespace" syntax at least for
show-trailing-whitespace.
Yes, that is true.
> 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.
What do you mean by "pattern" here? Regular expression?
Yes, I assumed it used one.
However, on second thought, I've concluded that
show-trailing-whitespace doesn't need to know about NBSP at all.
Since NBSP is now indicated on the screen by a color, it is no longer
likely to go unnoticed. So there is no problem with NBSP and
show-trailing-whitespace.
show-trailing-whitespace ought to know about all characters that will
be indistinguishable on the screen from "end of the line".
By the way, I've just found that currently the special face
for NBSP is overriden by show-trailing-whitespace.
Do you mean, show-trailing-whitespace would override the special face
for NBSP _if_ you modify it to recognize NBSP along with SPC and TAB?
That means my expectation was mistaken; I stand corrected.
But since show-trailing-whitespace does not need to recognize NBSP,
this isn't a _problem_.
Anyway, Unicode has lots more space-like characters
(e.g. U+2000..U+200B). Should them be treated by the same
way as NBSP (i.e. displayed with nobreak-face)? Or as
SPACE?
It depends how they are used. How does Emacs display them?
How about the case of fixup-whitespace? It seems that this
function should delete only TAB and SPACE. So, here we have
the third meaning of "whitespace"; just TAB and SPACE.
It is an interesting question what fixup-whitespace should do with
NBSP. I am not sure; it depends on how NBSP is used.
When the existing space is just one NBSP, fixup-whitespace should not
change it.
Do people use multiple NBSP to force more space between two words?
If so, maybe fixup-whitespace should leave that untouched. Or maybe
fixup-whitespace should convert a run of NBSP to a single NBSP.
When there is a series of whitespace including NBSP and SPC (or TAB),
the runs of ordinary whitespace should be compacted to a single SPC,
and the runs of NBSP should be treated as above.
Similar reasoning needs to be applied to other kinds of whitespace, to
figure out what behavior users will really find useful and helpful in
fixup-whitespace.
How about the case of delete-trailing-whitespace?
That is meant to get rid of junk. It should probably delete
NBSP just like SPC and TAB, since that is useless at the end of a line.
next prev parent reply other threads:[~2006-06-29 17:57 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
2006-06-29 2:01 ` Kenichi Handa
2006-06-29 17:57 ` Richard Stallman [this message]
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=E1Fw0li-00023u-6T@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@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.