Re: write-region saves in emacs-mule coding system thus unreadable to other programs

[Dan Jacobson]

>>>>> "S" == Simon says, via e-mail:
S> jidanni@kimo.FiXcomTHiS.tw (Dan Jacobson) writes:
>> Doing write-region or write-file inside a message-mode buffer saves it
>> in emacs-mule coding system instead of what the user expects, e.g.,
>> big5.   The non-Ascii text is then non readable without emacs.

S> I think this is intentional, because saving in message-mode is used to
S> save things (including auto-save) into the nndraft folder, and that is
S> should be in emacs-mule encoding because it doesn't MIME encode /
S> decode draft articles.

S> Anyway, it's configurable, see `message-draft-coding-system'.

S> I'm not sure if it's possible to change the default coding system for
S> the buffer and still have working (emacs-mule) auto-save
S> functionality.

OK, sounds tricky and I better not mess with it because I'm not a power
user.  However, I'm starting to worry that all the robustness and
portability of emacs backups and drafts that we knew and loved back in
the ASCII only days now are seemingly becoming locked in "emacs
proprietary formats" :-) that need emacs to unlock...

"The factory fire took the only [emacs user] computer whiz in the
company with it.  All we found was a #backup# copy of the manual he
was working on, but it was in some funny format that nobody in this
small country could unlock."
-- 
http://www.geocities.com/jidanni Tel+886-4-25854780 e-mail:restore .com.