From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: "Invalid coding system: ascii" when opening in external browser
Date: Mon, 18 Apr 2016 13:35:43 +0900 [thread overview]
Message-ID: <b4m1t63tty8.fsf@jpl.org> (raw)
In-Reply-To: <m260vj8ewx.fsf@krugs.de>
On Fri, 15 Apr 2016 10:17:02 +0200, Rainer M Krug wrote:
> https://www.dropbox.com/s/8a5hunvlhmj3ku1/TheMessage?dl=0
This looks like the one displayed in the article buffer, not
the raw html message. Please re-post it like this way:
Evaluate this form in the *scratch* buffer:
(type C-j at the end of the last line)
(progn
(put 'gnus-summary-write-to-file :decode nil)
(put 'gnus-summary-write-to-file :headers nil)
(setq gnus-save-all-headers t))
Do `M-x gnus-summary-write-article-file' for the message.
prev parent reply other threads:[~2016-04-18 4:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-14 10:00 Rainer M Krug
2016-04-14 14:42 ` Adam Sjøgren
2016-04-14 15:53 ` Rainer M Krug
2016-04-14 16:20 ` Adam Sjøgren
2016-04-15 8:17 ` Rainer M Krug
2016-04-18 4:35 ` Katsumi Yamaoka [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=b4m1t63tty8.fsf@jpl.org \
--to=yamaoka@jpl.org \
--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).