Re: scheme-mode+auto-fill-mode minor bug

[Dave Love]

Richard Stallman <address@hidden> writes:

> ~ in TeX bothers me somewhat, but I think the idea is that TeX mode
> should treat it like whitespace.

But that means potentially breaking at it, which is definitely not
what you want.

Re. previous mail:

Sorry I've just checked, and contrary to what I said before, no-break
space (codepoint 160 in iso-8859) _is_ treated as whitespace.  I
thought I'd changed it after discussion.  I think it should be
changed.

I also mis-remembered the entry in the Unicode database.  NO-BREAK
SPACE basically differs from SPACE in its decomposition
(non-character noBreak + SPACE, which isn't shown well by C-x =),
though the BIDI category is also different:

        character:   (0240, 160, 0xa0, U+00A0)
preferred charset: iso-8859-1 (Latin-1 (ISO/IEC 8859-1))
       code point: 160
           syntax: whitespace
         category: b:Arabic   l:Latin
      buffer code: 0xC2 0xA0
        file code: 0xA0 (encoded by coding system latin-1-unix)
    terminal code: 0xA0
     Unicode data:     
             Name: NO-BREAK SPACE
         Category: space separator
  Combining class: Spacing
    Bidi category: Common Number Separator
    Decomposition: noBreak
         Old name: NON-BREAKING SPACE