GNU bug report logs -
#47857
fill-paragraph vs. FULLWIDTH DIGITs: bug exposed
Previous Next
Reported by: 積丹尼 Dan Jacobson <jidanni <at> jidanni.org>
Date: Sun, 18 Apr 2021 01:13:03 UTC
Severity: minor
Tags: notabug
Done: Stefan Kangas <stefan <at> marxist.se>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 47857 in the body.
You can then email your comments to 47857 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#47857
; Package
emacs
.
(Sun, 18 Apr 2021 01:13:03 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
積丹尼 Dan Jacobson <jidanni <at> jidanni.org>
:
New bug report received and forwarded. Copy sent to
bug-gnu-emacs <at> gnu.org
.
(Sun, 18 Apr 2021 01:13:03 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
Disaster! M-q runs the command fill-paragraph
And turns:
Today's lucky number(s)!:
9
10
11
Into:
Today's lucky number(s)!:91011
OK, if it is so smart, then why doesn't it also turn:
Today's lucky number(s)!: 9 10 11
into:
Today's lucky number(s)!:91011
Well, surprise, it was actually very happy with 9 10 11 all along.
OK, let's add some space:
Today's lucky number(s)!: 9 10 11
becomes:
Today's lucky number(s)!: 9 10 11
perfect.
Anyway if it were stable in its output, then one would always get the same
results. Bug exposed!
(Yes, even LC_ALL isn't going to help. And yes, all this works fine if
all this was good old ASCII. emacs-version "27.1".)
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#47857
; Package
emacs
.
(Sun, 18 Apr 2021 06:54:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 47857 <at> debbugs.gnu.org (full text, mbox):
> From: 積丹尼 Dan Jacobson
> <jidanni <at> jidanni.org>
> Date: Sun, 18 Apr 2021 09:06:55 +0800
>
> Disaster! M-q runs the command fill-paragraph
>
> And turns:
>
> Today's lucky number(s)!:
> 9
> 10
> 11
>
> Into:
>
> Today's lucky number(s)!:91011
>
> OK, if it is so smart, then why doesn't it also turn:
>
> Today's lucky number(s)!: 9 10 11
>
> into:
>
> Today's lucky number(s)!:91011
>
> Well, surprise, it was actually very happy with 9 10 11 all along.
>
> OK, let's add some space:
> Today's lucky number(s)!: 9 10 11
> becomes:
> Today's lucky number(s)!: 9 10 11
> perfect.
>
> Anyway if it were stable in its output, then one would always get the same
> results. Bug exposed!
I don't see any bug here. This is the documented behavior: filling
deletes any excess whitespace, so 2 or more consecutive SPC characters
are squeezed to a single SPC. All the rest is a typical jidanni-style
hysteria.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#47857
; Package
emacs
.
(Sun, 18 Apr 2021 16:28:02 GMT)
Full text and
rfc822 format available.
Message #11 received at 47857 <at> debbugs.gnu.org (full text, mbox):
tags 47857 notabug
close 47857
thanks
Eli Zaretskii <eliz <at> gnu.org> writes:
> I don't see any bug here. This is the documented behavior: filling
> deletes any excess whitespace, so 2 or more consecutive SPC characters
> are squeezed to a single SPC. All the rest is a typical jidanni-style
> hysteria.
I'm therefore closing this bug.
Added tag(s) notabug.
Request was from
Stefan Kangas <stefan <at> marxist.se>
to
control <at> debbugs.gnu.org
.
(Sun, 18 Apr 2021 16:28:03 GMT)
Full text and
rfc822 format available.
bug closed, send any further explanations to
47857 <at> debbugs.gnu.org and 積丹尼 Dan Jacobson <jidanni <at> jidanni.org>
Request was from
Stefan Kangas <stefan <at> marxist.se>
to
control <at> debbugs.gnu.org
.
(Sun, 18 Apr 2021 16:28:03 GMT)
Full text and
rfc822 format available.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#47857
; Package
emacs
.
(Tue, 20 Apr 2021 01:14:02 GMT)
Full text and
rfc822 format available.
Message #18 received at 47857 <at> debbugs.gnu.org (full text, mbox):
EZ> I don't see any bug here. This is the documented behavior: filling
EZ> deletes any excess whitespace, so 2 or more consecutive SPC characters
EZ> are squeezed to a single SPC.
Ah, but one needs
Today's lucky number(s)!: <-added space here
9 <-added space here
10 <-added space here
11
to keep the whitespace in with fill-paragraph, whereas no spaces are
required for
Today's lucky number(s)!:
9
10
11
To safely become:
Today's lucky number(s)!: 9 10 11
(Also the value of enable-kinsoku has no effect here or in #47856,
which makes sense.)
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#47857
; Package
emacs
.
(Tue, 20 Apr 2021 11:30:02 GMT)
Full text and
rfc822 format available.
Message #21 received at 47857 <at> debbugs.gnu.org (full text, mbox):
> From: 積丹尼 Dan Jacobson <jidanni <at> jidanni.org>
> Cc: 47857 <at> debbugs.gnu.org
> Date: Tue, 20 Apr 2021 07:27:05 +0800
>
> EZ> I don't see any bug here. This is the documented behavior: filling
> EZ> deletes any excess whitespace, so 2 or more consecutive SPC characters
> EZ> are squeezed to a single SPC.
>
> Ah, but one needs
>
> Today's lucky number(s)!: <-added space here
> 9 <-added space here
> 10 <-added space here
> 11
>
> to keep the whitespace in with fill-paragraph, whereas no spaces are
> required for
>
> Today's lucky number(s)!:
> 9
> 10
> 11
>
> To safely become:
>
> Today's lucky number(s)!: 9 10 11
This is a feature: full-width Latin characters, such as 0, 1, and 9,
are exempted from converting newlines into spaces during filling.
They follow the rules of other CJK characters, which are processed the
same. I think it's because of line-breaking rules: we can break the
line between any 2 CJK characters, including those above, and thus
adding spaces where there were newlines is superfluous, as it would
artificially create separate words where only one has been before.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Wed, 19 May 2021 11:24:07 GMT)
Full text and
rfc822 format available.
This bug report was last modified 2 years and 335 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.