Re: No coding system in the modeline for unibyte buffers.

[Stefan Monnier <monnier@iro.umontreal.ca>]

> IIUC, a unibyte buffer should contain raw bytes, while a raw-text
> multibyte buffer would contain the same contents, converted to the
> internal utf-8 based Emacs representation.

Actually the raw-text part of a multibyte buffer only affects operation
when it is saved and loaded, so it can contain characters that are
not bytes.

> But I confess I'm puzzled why

>  M-x find-file-binary test.txt <RET>
>  M-: enable-multibyte-characters <RET>  => nil
>  C-u C-x =    ; over ñ

>         character:   (241, #o361, #xf1)
> preferred charset: iso-8859-1 (Latin-1 (ISO/IEC 8859-1))
>        code point: 0xF1
>            syntax: w 	which means: word
>          category: j:Japanese l:Latin
>       buffer code: #xC3 #xB1
>         file code: #xC3 #xB1 (encoded by coding system no-conversion)

> If I'm hopelessly wrong, I'm quite ready to be enlightened (and
> perhaps the docs will need work).

Indeed that's a bug in C-u C-x =.  It should pay attention to the
buffer's enable-multibyte-characters and then present #xf1 not as
a latin-1 char but as a raw-byte.


        Stefan