Re: should mbox be opened in unibyte mode

[Vladimir Volovich <vvv@vvv.vsu.ru>]

"JSB" == Janusz S Bien writes:

 JSB> What I wrote is about GNU Emacs and is based on its manual for
 JSB> version 20.6, the output of `describe-coding-system' and simple
 JSB> experiments with opening e.g. HELLO file with the `binary'
 JSB> coding system.

Here at home i only have GNU Emacs 20.4, and describe-coding-system
says about `binary':

= -- binary (alias of no-conversion)
  Do no conversion
Type: nil (do no conversion)
EOL type: LF

Perhaps, 20.6 has a more verbose description (which states in
particular that 'binary forces unibyte).

(btw, where i can access the current CVS emacs version for testing?)

 >> is the above about XEmacs or GNU Emacs? If it is about GNU Emacs,
 >> then why setting nnmbox-file-coding-system to 'binary does not
 >> switch off multibyte characters?

 JSB> Looks like some tracing should be done to check whether the
 JSB> values of `nnmbox-file-coding-system' and
 JSB> `nnmbox-active-file-coding-system' are really used when opening
 JSB> mbox.

It looks that they are not used when opening mbox. ;-(
(BTW, when a buffer is multibyte, C-x RET f binary RET is not supposed
to switch to unibyte mode, right? only opening a file with a binary
mode (C-x RET c binary RET C-x C-f filename RET) does this?)

	Best regards, -- Vladimir.