From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: Never automatically display HTML in an email
Date: Wed, 06 Jun 2018 11:06:06 -0700 [thread overview]
Message-ID: <8736xzvlgx.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <868t7r3jfg.fsf@zoho.com>
Emanuel Berg <moasen@zoho.com> writes:
> Eric Abrahamsen wrote:
>
>> And thanks for the summary! I stole some
>> config from that (Gnus mime has always been
>> a black box as far as I'm concerned).
>
> Question remains why this should be so
> complicated, especially since a lot of people
> seem to want it. Or is it just the "true
> hacker" audience of this newsgroup?
>
> Anyway, perhaps synthetise into a
>
> (setq gnus-article-down-with-html t)
>
> ?
Beats me, really. Personally, part of it is that I don't work with
mime-types all that often, and keep forgetting the terminology.
The "Using MIME" and "MIME Commands" sections of the Gnus manual get you
part-way there, but then you fall down the rabbit-hole of the separate
"Emacs MIME" manual, and there goes your Thursday night. I eventually
got mad and hit it with a hammer:
(setq mailcap-mime-data
'(("application" (".*" (viewer . "xdg-open %s")))))
But occasionally that still causes errors and complaints about a lack of
a "text/plain" part or something like that, I'm still too annoyed to go
and figure out what's going on. Attempts to "follow the code" result in
near-instant headaches.
Eric
next prev parent reply other threads:[~2018-06-06 18:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-01 4:02 Chris Marusich
2018-06-01 8:00 ` Malcolm Purvis
2018-06-05 7:27 ` Chris Marusich
2018-06-05 15:24 ` Jorge A. Alfaro-Murillo
2018-06-05 15:33 ` Emanuel Berg
2018-06-06 4:42 ` Chris Marusich
2018-06-06 16:58 ` Eric Abrahamsen
2018-06-06 17:37 ` Emanuel Berg
2018-06-06 18:06 ` Eric Abrahamsen [this message]
2018-06-06 18:41 ` Emanuel Berg
2018-06-06 18:51 ` Eric Abrahamsen
2018-06-05 19:01 ` Andreas Schwab
2018-06-01 8:05 ` Andreas Schwab
2018-06-01 9:27 ` Adam Sjøgren
2018-06-01 11:56 ` Emanuel Berg
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=8736xzvlgx.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).