From: Jordan Wilson <jordan.t.wilson@gmx.com>
To: info-gnus-english@gnu.org
Subject: Re: "Forward" in the standard way
Date: Sat, 14 Apr 2018 12:38:40 +0100 [thread overview]
Message-ID: <8736zyaugv.fsf@gmx.com> (raw)
In-Reply-To: <87a8m2f8ra.fsf@gmx.com>
[-- Attachment #1: Type: text/plain, Size: 852 bytes --]
On 2016-03-13 (Sun) at 20:00 (+0000), I wrote:
> I have been trying to forward HTML email (*makes the sign of the
> cross*).
>
> I want to have Gnus treat the email content "in the standard way",
> i.e. have the HTML content inline (not as an attachment), and renderable
> by non-Gnus email clients.
>
> My fiddlings with `message-forward-as-mime' and
> `message-forward-show-mml' has got me as far as having the
> HTML message inline, but the HTML is unrendered on the other end.
>
> Is there a simple way of doing this using Gnus?
I completely forgot about this thread, until just now seeing Lars's reply.
I ended up hacking together this very ugly function (more of a
script). I imagine it would have been trivial to implement this
properly, but didn't have the time to look at Gnus' internals. It works
most of the time in the way that I wanted.
[-- Attachment #2: html-forward.el --]
[-- Type: application/emacs-lisp, Size: 1496 bytes --]
[-- Attachment #3: Type: text/plain, Size: 41 bytes --]
--
Sent from Gnus v5.13, GNU Emacs 26.1
next prev parent reply other threads:[~2018-04-14 11:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-13 20:00 Jordan Wilson
2016-03-13 20:31 ` Adam Sjøgren
2016-03-13 20:41 ` Jordan Wilson
2016-03-13 20:44 ` Adam Sjøgren
2016-04-06 8:02 ` Elias Mårtenson
2016-04-06 8:46 ` Adam Sjøgren
2016-04-06 11:04 ` Eric S Fraga
2016-04-06 12:53 ` Rasmus
2016-04-09 3:38 ` Elias Mårtenson
2016-04-09 9:33 ` Adam Sjøgren
2016-04-09 9:37 ` Adam Sjøgren
[not found] ` <mailman.127.1460173141.7477.info-gnus-english@gnu.org>
2018-04-10 22:01 ` Lars Ingebrigtsen
2018-04-14 11:38 ` Jordan Wilson [this message]
2018-04-14 18:00 ` Lars Ingebrigtsen
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=8736zyaugv.fsf@gmx.com \
--to=jordan.t.wilson@gmx.com \
--cc=info-gnus-english@gnu.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).