From: Alberto Luaces <aluaces@udc.es>
To: info-gnus-english@gnu.org
Subject: Re: How strip attached images `en masse'
Date: Fri, 15 Oct 2010 09:26:08 +0200 [thread overview]
Message-ID: <87tyknvrvz.fsf@eps142.cdf.udc.es> (raw)
In-Reply-To: <87ocawa5dd.fsf@newsguy.com>
Harry Putnam writes:
> Can any one offer some input on commands for writing attachments to
> disk that work on a mass level rather one at a time.
>
> I normally use `K o' to write an image to disk but that is going to be
> very tedious with the mass of images I'm now receiving.
>
> The command requires that I leave the summary buffer and move to the
> article buffer then move point to the attached item, them press `K o'
> and give a file name.
>
> That will not do it for some 100 images over several messages.
From the summary buffer you have `gnus-summary-save-parts', bound to `X
m'. Maybe you can craft a simple macro for operating on several
messages.
--
Alberto
next prev parent reply other threads:[~2010-10-15 7:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-14 20:25 Harry Putnam
2010-10-15 7:26 ` Alberto Luaces [this message]
[not found] <mailman.4.1287087970.17933.info-gnus-english@gnu.org>
2010-10-14 20:47 ` Jason Earl
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=87tyknvrvz.fsf@eps142.cdf.udc.es \
--to=aluaces@udc.es \
--cc=info-gnus-english@gnu.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).