From: era eriksson <era+gmane@iki.fi>
Subject: Wishlist: gnus-summary-save-parts: save all parts
Date: Wed, 12 Apr 2006 09:57:30 +0000 (UTC) [thread overview]
Message-ID: <loom.20060412T114800-795@post.gmane.org> (raw)
On a message with multiple message/rfc822 attachments, I found that `X m' would
only save the last part (possibly it saved the earlier parts under the same
name, or something). It would seem that it is useful only when each part has a
filename= or name= parameter.
It would be useful and probably closer to user expectations if it could come up
with a unique name for each part which doesn't otherwise have one.
As a workaround, running Esc 2 K o (filename) RET, Esk 3 K o (filename) RET etc
works when you have a small number of attachments. Then you get to name each
file on the fly.
For a message with 61 attachments, I came up with the following M-x eval:
(let ((i 2)) (while (< i 63)
;; This snippet divinely inspired by code from from gnus-sum.el and mm-decode.el
(set-buffer gnus-article-buffer)
(gnus-article-goto-part i)
(mm-save-part-to-file
(cdr (assq i gnus-article-mime-handle-alist))
(concat "/tmp/parts/" (int-to-string i) ".msg"))
(setq i (1+ i)) ) )
Obviously, this could be generalized to a function which loops exactly as many
times as required for each message, asks for a directory name and/or perhaps a
filename template, checks that the directory exists, etc.
I had a quick look at the current CVS sources on Quimby, and could not see any
changes to the parts of the code where this is handled, compared to what I have
in my Gnus 5.10 on Ubuntu Breezy ("Version: 5.10.6-0.CVS.20050610-1")
/* era */
--
If this were a real .signature, it would suck less. Well, maybe not.
next reply other threads:[~2006-04-12 9:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-12 9:57 era eriksson [this message]
[not found] <mailman.336.1144837227.9609.info-gnus-english@gnu.org>
2006-04-12 10:44 ` Lars Magne Ingebrigtsen
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=loom.20060412T114800-795@post.gmane.org \
--to=era+gmane@iki.fi \
/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).