From: Uwe Brauer <oub@mat.ucm.es>
To: ding@gnus.org
Cc: XEmacs Beta Discussion <xemacs-beta@xemacs.org>
Subject: Xemacs (Mule) and GNU Emacs, problem with drafts and encoding.
Date: Wed, 27 May 2015 14:51:12 +0200 [thread overview]
Message-ID: <87pp5m5glb.fsf@mat.ucm.es> (raw)
Hello
I use gnus with both Emacsen. However the drafts which are saved are not
compatible with each other.
According to the documentation"
,----
|
| `message-draft-coding-system' is a variable declared in Lisp.
| -- loaded from "message"
|
| Value: escape-quoted
|
| 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.
`----
I tried that but this coding setting but alas it does not make the
drafts compatible.
Why does Xemacs not support the utf-8 coding for drafts, although in
general it does support this format?
regards
Uwe Brauer
next reply other threads:[~2015-05-27 12:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 12:51 Uwe Brauer [this message]
2015-05-28 1:29 ` Katsumi Yamaoka
2015-05-28 9:26 ` Uwe Brauer
2015-05-29 2:46 ` Katsumi Yamaoka
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=87pp5m5glb.fsf@mat.ucm.es \
--to=oub@mat.ucm.es \
--cc=ding@gnus.org \
--cc=xemacs-beta@xemacs.org \
/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).