* bug#1727: 23.0.60; end-of-sentence and non-breaking space
[not found] <87y6xv7kmc.fsf@cyd.mit.edu>
@ 2009-01-02 1:25 ` Richard M Stallman
2009-01-02 1:25 ` bug#1726: " Richard M Stallman
` (4 subsequent siblings)
5 siblings, 0 replies; 7+ messages in thread
From: Richard M Stallman @ 2009-01-02 1:25 UTC (permalink / raw)
To: Chong Yidong; +Cc: 1726, 1727, emacs-devel
> When I type C-x = at a non-breaking space, it tells me that it
> has code 160, hex a0. But when I execute (insert "\xa0"),
> it inserts something that displays as `\240' and for which C-x =
> displays this:
> Char: (4194208, #o17777640, #x3fffa0, raw-byte) point=198 of 211
> (93%) column=5
>
> Is that a bug? It seems quite confusing to me.
ISTR that there was an extended discussion about classifying
non-breaking spaces on this list a while back. But I can't find it now.
Does anyone remember the details?
I am not sure we are talking about the same question.
The issue I am raising is not one of classifying it,
it is that these two different character codes get used
and I don't see an explanation of what's going on.
^ permalink raw reply [flat|nested] 7+ messages in thread
* bug#1726: 23.0.60; end-of-sentence and non-breaking space
[not found] <87y6xv7kmc.fsf@cyd.mit.edu>
2009-01-02 1:25 ` bug#1727: 23.0.60; end-of-sentence and non-breaking space Richard M Stallman
@ 2009-01-02 1:25 ` Richard M Stallman
2009-01-02 2:38 ` bug#1726: bug#1727: " Drew Adams
` (3 subsequent siblings)
5 siblings, 0 replies; 7+ messages in thread
From: Richard M Stallman @ 2009-01-02 1:25 UTC (permalink / raw)
To: Chong Yidong; +Cc: 1726, 1727, emacs-devel
> When I type C-x = at a non-breaking space, it tells me that it
> has code 160, hex a0. But when I execute (insert "\xa0"),
> it inserts something that displays as `\240' and for which C-x =
> displays this:
> Char: (4194208, #o17777640, #x3fffa0, raw-byte) point=198 of 211
> (93%) column=5
>
> Is that a bug? It seems quite confusing to me.
ISTR that there was an extended discussion about classifying
non-breaking spaces on this list a while back. But I can't find it now.
Does anyone remember the details?
I am not sure we are talking about the same question.
The issue I am raising is not one of classifying it,
it is that these two different character codes get used
and I don't see an explanation of what's going on.
^ permalink raw reply [flat|nested] 7+ messages in thread
* bug#1726: bug#1727: 23.0.60; end-of-sentence and non-breaking space
[not found] <87y6xv7kmc.fsf@cyd.mit.edu>
2009-01-02 1:25 ` bug#1727: 23.0.60; end-of-sentence and non-breaking space Richard M Stallman
2009-01-02 1:25 ` bug#1726: " Richard M Stallman
@ 2009-01-02 2:38 ` Drew Adams
2009-01-02 2:38 ` Drew Adams
` (2 subsequent siblings)
5 siblings, 0 replies; 7+ messages in thread
From: Drew Adams @ 2009-01-02 2:38 UTC (permalink / raw)
To: 'Chong Yidong', 1727, emacs-devel; +Cc: 1726, rms
> ISTR that there was an extended discussion about classifying
> non-breaking spaces on this list a while back. But I can't
> find it now. Does anyone remember the details?
Dunno if this is what you were thinking of, but there was this discussion about
treating (classifying) nonbreaking space as whitespace:
http://lists.gnu.org/archive/html/emacs-devel/2007-06/msg01089.html
^ permalink raw reply [flat|nested] 7+ messages in thread
* bug#1727: 23.0.60; end-of-sentence and non-breaking space
[not found] <87y6xv7kmc.fsf@cyd.mit.edu>
` (2 preceding siblings ...)
2009-01-02 2:38 ` bug#1726: bug#1727: " Drew Adams
@ 2009-01-02 2:38 ` Drew Adams
2009-01-02 4:11 ` bug#1726: " Stefan Monnier
2009-01-02 4:11 ` bug#1727: " Stefan Monnier
5 siblings, 0 replies; 7+ messages in thread
From: Drew Adams @ 2009-01-02 2:38 UTC (permalink / raw)
To: 'Chong Yidong', 1727, emacs-devel; +Cc: 1726, rms
> ISTR that there was an extended discussion about classifying
> non-breaking spaces on this list a while back. But I can't
> find it now. Does anyone remember the details?
Dunno if this is what you were thinking of, but there was this discussion about
treating (classifying) nonbreaking space as whitespace:
http://lists.gnu.org/archive/html/emacs-devel/2007-06/msg01089.html
^ permalink raw reply [flat|nested] 7+ messages in thread
* bug#1726: 23.0.60; end-of-sentence and non-breaking space
[not found] <87y6xv7kmc.fsf@cyd.mit.edu>
` (3 preceding siblings ...)
2009-01-02 2:38 ` Drew Adams
@ 2009-01-02 4:11 ` Stefan Monnier
2009-01-02 4:11 ` bug#1727: " Stefan Monnier
5 siblings, 0 replies; 7+ messages in thread
From: Stefan Monnier @ 2009-01-02 4:11 UTC (permalink / raw)
To: Chong Yidong; +Cc: 1726, 1727, rms, emacs-devel
>> has code 160, hex a0. But when I execute (insert "\xa0"),
>> it inserts something that displays as `\240' and for which C-x =
>> displays this:
>>
>> Char: (4194208, #o17777640, #x3fffa0, raw-byte) point=198 of 211
>> (93%) column=5
>>
>> Is that a bug? It seems quite confusing to me.
This raw-byte char is what used to be called an eight-bit-control (or
eight-bit-graphic depending on the actual value) char.
I.e. "\xa0" is treated as a string that contains the \xa0 byte (i.e. an
eight-bit-* (aka raw-byte) char) rather than the \xa0 char (a latin-1
non-breaking space).
Stefan
^ permalink raw reply [flat|nested] 7+ messages in thread
* bug#1727: 23.0.60; end-of-sentence and non-breaking space
[not found] <87y6xv7kmc.fsf@cyd.mit.edu>
` (4 preceding siblings ...)
2009-01-02 4:11 ` bug#1726: " Stefan Monnier
@ 2009-01-02 4:11 ` Stefan Monnier
5 siblings, 0 replies; 7+ messages in thread
From: Stefan Monnier @ 2009-01-02 4:11 UTC (permalink / raw)
To: Chong Yidong; +Cc: 1726, 1727, rms, emacs-devel
>> has code 160, hex a0. But when I execute (insert "\xa0"),
>> it inserts something that displays as `\240' and for which C-x =
>> displays this:
>>
>> Char: (4194208, #o17777640, #x3fffa0, raw-byte) point=198 of 211
>> (93%) column=5
>>
>> Is that a bug? It seems quite confusing to me.
This raw-byte char is what used to be called an eight-bit-control (or
eight-bit-graphic depending on the actual value) char.
I.e. "\xa0" is treated as a string that contains the \xa0 byte (i.e. an
eight-bit-* (aka raw-byte) char) rather than the \xa0 char (a latin-1
non-breaking space).
Stefan
^ permalink raw reply [flat|nested] 7+ messages in thread