From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Jonathan Yavner <jyavner@rogers.com>,
juri@jurta.org, emacs-devel@gnu.org
Subject: Re: shouldn't `delete-blank-lines' treat form-feed as whitespace?
Date: Sun, 07 Mar 2010 14:08:21 +0900 [thread overview]
Message-ID: <87ocj0u3ay.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <83wrxo3gzj.fsf@gnu.org>
Eli Zaretskii writes:
> How is the line-breaking property relevant to this function? The doc
> string says just "delete all surrounding blank lines". It doesn't
> mention line-breaking at all. The question is, should a line
> consisting only of NBSP characters be considered a blank line.
My understanding of the Unicode standard is that whitespace characters
are blanks. Interestingly enough, however, in many cases they are
treated as non-blank characters that happen to be extremely
conservative of ink. :-) Eg, one oftens see the "<TAG> </TAG>"
idiom in HTML (especially in TD elements).
Nevertheless, I think NBSP ought to be treated as a blank for the
purpose of `delete-blank-lines'.
next prev parent reply other threads:[~2010-03-07 5:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1No0yT-0007vs-HZ@mail.fsf.org>
2010-03-06 22:34 ` shouldn't `delete-blank-lines' treat form-feed as whitespace? Jonathan Yavner
2010-03-07 4:14 ` Eli Zaretskii
2010-03-07 4:34 ` Jonathan Yavner
2010-03-07 17:42 ` Eli Zaretskii
2010-03-07 18:11 ` Stephen J. Turnbull
2010-03-07 5:08 ` Stephen J. Turnbull [this message]
2010-02-28 20:44 Drew Adams
2010-03-03 19:32 ` Juri Linkov
2010-03-03 19:54 ` Drew Adams
2010-03-04 4:28 ` Stefan Monnier
2010-03-05 8:48 ` Eli Zaretskii
2010-03-06 17:57 ` Juri Linkov
2010-03-06 18:56 ` Eli Zaretskii
2010-03-03 21:35 ` David De La Harpe Golden
2010-03-03 22:21 ` Drew Adams
2010-03-04 1:40 ` Miles Bader
2010-03-04 6:21 ` Drew Adams
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=87ocj0u3ay.fsf@uwakimon.sk.tsukuba.ac.jp \
--to=stephen@xemacs.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=juri@jurta.org \
--cc=jyavner@rogers.com \
/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.