From: Pankaj Jangid <pankaj@codeisgreat.org>
To: ding@gnus.org
Subject: Re: [gnus-summary-save-parts does NOT respect file names]
Date: Fri, 21 May 2021 21:16:53 +0530 [thread overview]
Message-ID: <m2h7iwum1e.fsf@codeisgreat.org> (raw)
In-Reply-To: <87h7iwny8p.fsf@mat.ucm.es>
Uwe Brauer <oub@mat.ucm.es> writes:
>> I just tried it using the ‘X m’ shortcut. It saved all attachments with
>> the original names. I am using Emacs-28 from the ‘master’ branch.
>
> So do I! Emacs28 master. Where do you use this function in the message
> or in the summary buffer?
>
> Do you use the imap backend?
I used it from summary buffer and I am using IMAP backend.
next prev parent reply other threads:[~2021-05-21 15:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-21 6:30 download all attachments in one go Uwe Brauer
2021-05-21 6:39 ` [gnus-summary-save-parts does NOT respect file names] (was: download all attachments in one go) Uwe Brauer
2021-05-21 9:19 ` [gnus-summary-save-parts does NOT respect file names] Pankaj Jangid
2021-05-21 11:05 ` Uwe Brauer
2021-05-21 15:46 ` Pankaj Jangid [this message]
2021-05-22 5:32 ` Pankaj Jangid
2021-05-22 5:39 ` Emanuel Berg
2021-05-22 17:15 ` Uwe Brauer
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=m2h7iwum1e.fsf@codeisgreat.org \
--to=pankaj@codeisgreat.org \
--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).