From: Uwe Brauer <oub@mat.ucm.es>
To: ding@gnus.org
Subject: [SOLVED] (was: message with large attachments: just display)
Date: Tue, 21 Jul 2020 22:43:24 +0200 [thread overview]
Message-ID: <87blk8vbtf.fsf@mat.ucm.es> (raw)
In-Reply-To: <87h7u0vcel.fsf@mat.ucm.es>
[-- Attachment #1: Type: text/plain, Size: 409 bytes --]
>>> "UB" == Uwe Brauer <oub@mat.ucm.es> writes:
> Hi
> When I want to open a message with an attachment, say of 20 MB, gnus
> takes forever to open the message, which gives me the feeling that he is
> trying to put some information in some sort of cache. How can I avoid
> that and speed up reading?
It seems that
(nnimap-fetch-partial-articles "text/")
Does the trick
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]
prev parent reply other threads:[~2020-07-21 20:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-21 20:30 message with large attachments: just display Uwe Brauer
2020-07-21 20:43 ` Uwe Brauer [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=87blk8vbtf.fsf@mat.ucm.es \
--to=oub@mat.ucm.es \
--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).