From: Uwe Brauer <oub@mat.ucm.es>
To: ding@gnus.org
Subject: gnus-summary-save-article: Xemacs better than GNU emacs?
Date: Thu, 24 Mar 2016 13:20:07 +0000 [thread overview]
Message-ID: <87twjw9fnc.fsf@mat.ucm.es> (raw)
Hello
I am using GNU emacs 25.1.50.1
and mua-gnus 0.16.
Using GNU emacs
I have set
(setq gnus-default-article-saver 'gnus-summary-save-in-file)
and saved a message,
Now when I opened the file with GNU emacs it looked terrible a lot of
chars such as (not printable)
\342\200\213 ....
now when I opened it with Xemacs (21.5.34 Mule) it looked ok
I attach both screenshots, in the next message, since I am not sure
whether otherwise the message gets trapped by the SPAM filter.
I am not sure who is here the culprit, because
I had difficulties to open UTF8 files in GNU emacs which contains such
chars. Maybe GNU emacs is stricter with respect to UTF* than Xemacs?
Uwe Brauer
next reply other threads:[~2016-03-24 13:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-24 13:20 Uwe Brauer [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-03-24 9:48 gnus-summary-save-article: xemacs " Uwe Brauer
2016-03-25 1:08 ` Eric Abrahamsen
2016-03-25 9:01 ` Uwe Brauer
2016-03-25 9:21 ` Eric Abrahamsen
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=87twjw9fnc.fsf@mat.ucm.es \
--to=oub@mat.ucm.es \
--cc=ding@gnus.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).