From: "Adam Sjøgren" <asjo@koldfront.dk>
To: ding@gnus.org
Subject: Automatically displaying content of [some] attachments
Date: Sat, 15 Aug 2020 12:12:03 +0200 [thread overview]
Message-ID: <87wo20b4lo.fsf@tullinup.koldfront.dk> (raw)
I often receive emails with gzip'ed/zip'ed attachments, like this:
[1. application/zip; google.com!asjo.org!1597363200!1597449599.zip]...
[2. application/tlsrpt+gzip; google.com!koldfront.dk!1597363200!1597449599!001.json.gz]...
If I press RET on them, they are expanded (decompressed and content
shown in the buffer), which is nice.
What do I need to configure to have that done automatically, so I don't
have to navigate to the attachment and press RET?
I have been looking in mm-decode.el, but so far I haven't hit the right
combination.
Best regards,
Adam
--
"Thanks to enzymes, humans are solar-powered." Adam Sjøgren
asjo@koldfront.dk
next reply other threads:[~2020-08-15 10:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-15 10:12 Adam Sjøgren [this message]
2020-08-15 10:45 ` Adam Sjøgren
2020-08-15 10:51 ` Adam Sjøgren
2020-08-15 18:41 ` Wayne Harris
2020-08-15 20:40 ` Adam Sjøgren
2020-08-19 1:50 ` Wayne Harris
2020-08-19 20:02 ` Adam Sjøgren
2020-08-20 2:21 ` Rafi Khan
2020-08-25 9:30 ` Eric S Fraga
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=87wo20b4lo.fsf@tullinup.koldfront.dk \
--to=asjo@koldfront.dk \
--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).