From: Eric Abrahamsen <email@example.com> To: "Tassilo Horn" <firstname.lastname@example.org> Cc: "Adam Sjøgren" <email@example.com>, firstname.lastname@example.org Subject: Re: (not downloaded, A C to fetch.) on empty part Date: Wed, 29 Jul 2020 09:16:57 -0700 Message-ID: <email@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> (Tassilo Horn's message of "Wed, 29 Jul 2020 18:12:06 +0200") "Tassilo Horn" <email@example.com> writes: >> > I just recieved a multipart MIME email with an empty text/html part. >> > Gnus shows it as: >> > >> > [1. text/html (not downloaded, A C to fetch.)] >> > >> > A C makes no sense here, as I am using nnml as the backend. >> > >> > Some logic awry for non-imap backends? >> >> This was an addition by Tassilo in 659ed857c, whom I'm copying here -- >> it does sound like there's some cross-backend bleed-over? > > I added that to any mail containing an empty part because a partial > fetch seemed to be the only reason for encountering such a part except > for a broken mail and then this text is as good as any other. > > I can check if I can omit the button text if we're on a non-imap > backend or partial fetches are not configured. But that has to wait a > bit. I'm away from the computer till Wednesday next week. nnimap is the only backend that supports partial fetching of articles, right? I wonder how hard it would be to detect an empty part and say that, instead. I try to stay away from the mime code. Anyhow, no big emergency.
next prev parent reply index Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-29 13:31 Adam Sjøgren 2020-07-29 15:53 ` Eric Abrahamsen 2020-07-29 16:12 ` Tassilo Horn 2020-07-29 16:16 ` Eric Abrahamsen [this message] 2020-07-29 16:28 ` Tassilo Horn 2020-07-29 16:46 ` Eric Abrahamsen 2020-08-06 19:54 ` Tassilo Horn 2020-08-06 20:01 ` Eric Abrahamsen 2020-08-06 20:08 ` Adam Sjøgren 2020-07-29 16:30 ` Adam Sjøgren
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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.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
Gnus development mailing list Archives are clonable: git clone --mirror http://inbox.vuxu.org/ding Example config snippet for mirrors Newsgroup available over NNTP: nntp://inbox.vuxu.org/vuxu.archive.emacs.gnus.general AGPL code for this site: git clone https://public-inbox.org/public-inbox.git