From: Reiner Steib <4.uce.03.r.s@nurfuerspam.de>
Subject: Re: Something about charsets is broken in message mode
Date: Tue, 09 Dec 2003 19:52:41 +0100 [thread overview]
Message-ID: <v9iskpu8li.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <m3vfopc22n.fsf@fed1.frank-schmitt.net>
On Tue, Dec 09 2003, Frank Schmitt wrote:
> If I say C-h v buffer-file-coding-system in a message buffer the
> value is emacs-mule-dos as well as I'm on a Unix system.
Cannot reproduce this here (with CVS-Head-Emacs of 2003-11-25 or
21.3). I get ...
,----
| = -- emacs-mule
| Emacs internal format used in buffer and string.
| [...]
|
| Type: 0 (Emacs internal multibyte form)
| EOL type: Automatic selection from:
| [emacs-mule-unix emacs-mule-dos emacs-mule-mac]
`----
> Could the reason be, that I use my old mail folders from Windows?
Dunno. Does it happen only when re-editing old "DOS-drafts" or
replying to old mail?
> BTW: Outgoing mails and news are encoded in UTF-8 as I say
> (setq mm-coding-system-priorities '(mule-utf-8)) in .gnus.
> Wouldn't it make much more sense to save drafts in Unicode, too?
Probably this will break XEmacs (Cf. the changes around 2002-11-06.).
,----[ C-h v message-draft-coding-system RET ]
| message-draft-coding-system's value is emacs-mule
|
| Documentation:
| *Coding system to compose mail.
| If you'd like to make it possible to share draft files between XEmacs
| and Emacs, you may use `iso-2022-7bit' for this value at your own risk.
| Note that the coding-system `iso-2022-7bit' isn't suitable to all data.
|
| Defined in `message'.
`----
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- PGP key available via WWW http://rsteib.home.pages.de/
prev parent reply other threads:[~2003-12-09 18:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-09 17:50 Frank Schmitt
2003-12-09 18:52 ` Reiner Steib [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=v9iskpu8li.fsf@marauder.physik.uni-ulm.de \
--to=4.uce.03.r.s@nurfuerspam.de \
--cc=reiner.steib@gmx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).