From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: gnus-summary-save-article: xemacs better than GNU emacs?
Date: Fri, 25 Mar 2016 09:08:59 +0800 [thread overview]
Message-ID: <874mbvs6s4.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <8760wcb40f.fsf@mat.ucm.es>
Uwe Brauer <oub@mat.ucm.es> writes:
> 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 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?
Check the docstring of `gnus-default-article-saver'. It mentions that
the function symbols that that option points to can have properties, one
of which is :decode. I'm guessing this is the source of your issue.
(get 'gnus-summary-save-in-file :decode)-->t
Maybe play with that and see if it fixes the issue?
E
next prev parent reply other threads:[~2016-03-25 1:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-24 9:48 Uwe Brauer
2016-03-25 1:08 ` Eric Abrahamsen [this message]
2016-03-25 9:01 ` Uwe Brauer
2016-03-25 9:21 ` Eric Abrahamsen
2016-03-24 13:20 gnus-summary-save-article: Xemacs " Uwe Brauer
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=874mbvs6s4.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--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).