From: "Clément Pit-Claudel" <cpitclaudel@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: lisp/term/ns-win.el modification
Date: Sun, 30 Apr 2017 11:06:08 -0400 [thread overview]
Message-ID: <5d3d3f3d-e49e-2b83-0591-14b3e19f8cb0@gmail.com> (raw)
In-Reply-To: <83inlmkmqq.fsf@gnu.org>
On 2017-04-30 10:12, Eli Zaretskii wrote:
>> From: Jean-Christophe Helary <jean.christophe.helary@gmail.com>
>> Date: Sun, 30 Apr 2017 15:41:45 +0900
>>
>>> Besides, it doesn't trim non-breakable spaces.
>>
>> That's a pity. Is there a reason why non-breakable spaces would not be considered for trimming purposes?
>
> What's the rationale for adding NBSP? Also, is it only the NBSP
> character that's missing, or there are others?
Possibly for consistency with other languages. Here's what Python 3 does:
import sys
import unicodedata
for codepoint in range(sys.maxunicode + 1):
c = chr(codepoint)
if c.strip() == "":
name = unicodedata.name(c, "U+{:04X}".format(codepoint))
print("Python 3 trims {} ({})".format(name, unicodedata.category(c)))
Python 3 trims U+0009 (Cc)
Python 3 trims U+000A (Cc)
Python 3 trims U+000B (Cc)
Python 3 trims U+000C (Cc)
Python 3 trims U+000D (Cc)
Python 3 trims U+001C (Cc)
Python 3 trims U+001D (Cc)
Python 3 trims U+001E (Cc)
Python 3 trims U+001F (Cc)
Python 3 trims SPACE (Zs)
Python 3 trims U+0085 (Cc)
Python 3 trims NO-BREAK SPACE (Zs)
Python 3 trims OGHAM SPACE MARK (Zs)
Python 3 trims EN QUAD (Zs)
Python 3 trims EM QUAD (Zs)
Python 3 trims EN SPACE (Zs)
Python 3 trims EM SPACE (Zs)
Python 3 trims THREE-PER-EM SPACE (Zs)
Python 3 trims FOUR-PER-EM SPACE (Zs)
Python 3 trims SIX-PER-EM SPACE (Zs)
Python 3 trims FIGURE SPACE (Zs)
Python 3 trims PUNCTUATION SPACE (Zs)
Python 3 trims THIN SPACE (Zs)
Python 3 trims HAIR SPACE (Zs)
Python 3 trims LINE SEPARATOR (Zl)
Python 3 trims PARAGRAPH SEPARATOR (Zp)
Python 3 trims NARROW NO-BREAK SPACE (Zs)
Python 3 trims MEDIUM MATHEMATICAL SPACE (Zs)
Python 3 trims IDEOGRAPHIC SPACE (Zs)
Clément.
next prev parent reply other threads:[~2017-04-30 15:06 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-27 4:50 lisp/term/ns-win.el modification Jean-Christophe Helary
2017-04-27 9:02 ` Anders Lindgren
2017-04-27 10:13 ` Jean-Christophe Helary
2017-04-27 11:30 ` Anders Lindgren
2017-04-27 14:53 ` Jean-Christophe Helary
2017-04-27 15:09 ` Davis Herring
2017-04-27 15:31 ` Jean-Christophe Helary
2017-04-27 23:32 ` Jean-Christophe Helary
[not found] ` <15112485-03CC-4FFF-8A9D-BA28D2490A91-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-04-28 1:49 ` Jean-Christophe Helary
2017-04-29 12:24 ` Anders Lindgren
[not found] ` <CABr8ebaB1Fp0BgVy7LWwtOnSs1UOXr3CJumMfOWR4JOooQMT4g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-04-29 12:49 ` Jean-Christophe Helary
2017-04-30 5:36 ` Anders Lindgren
2017-04-30 12:14 ` Noam Postavsky
2017-04-30 6:41 ` Jean-Christophe Helary
2017-04-30 14:12 ` Eli Zaretskii
2017-04-30 15:06 ` Clément Pit-Claudel [this message]
2017-04-30 15:24 ` Eli Zaretskii
2017-04-30 22:28 ` Jean-Christophe Helary
2017-05-01 6:33 ` Eli Zaretskii
2017-05-01 8:23 ` Jean-Christophe Helary
2017-05-01 8:59 ` Eli Zaretskii
2017-05-01 10:53 ` Jean-Christophe Helary
2017-05-01 11:27 ` Eli Zaretskii
2017-05-02 4:00 ` Jean-Christophe Helary
2017-05-02 6:44 ` Eli Zaretskii
2017-05-02 6:47 ` Jean-Christophe Helary
2017-05-01 15:12 ` Jean-Christophe Helary
2017-05-01 15:27 ` Eli Zaretskii
2017-05-01 15:58 ` Jean-Christophe Helary
2017-05-01 16:25 ` Eli Zaretskii
2017-05-02 12:57 ` Jean-Christophe Helary
2017-05-03 20:40 ` Anders Lindgren
2017-05-04 0:10 ` Jean-Christophe Helary
2017-05-04 8:50 ` Jean-Christophe Helary
2017-05-04 18:37 ` Anders Lindgren
2017-05-05 8:36 ` Jean-Christophe Helary
2017-04-30 22:23 ` Jean-Christophe Helary
2017-05-01 6:30 ` Eli Zaretskii
2017-04-27 12:24 ` Noam Postavsky
2017-04-27 14:53 ` Jean-Christophe Helary
2017-04-27 12:51 ` mituharu
2017-04-27 14:55 ` Jean-Christophe Helary
2017-04-27 15:35 ` Jean-Christophe Helary
2017-04-27 18:28 ` mituharu
2017-04-27 23:29 ` Jean-Christophe Helary
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=5d3d3f3d-e49e-2b83-0591-14b3e19f8cb0@gmail.com \
--to=cpitclaudel@gmail.com \
--cc=emacs-devel@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 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.