From: David Hanak <dhanakDONT@isisSEND.vanderbiltME.eduSPAM>
Subject: Re: Saving an Attachment?
Date: Thu, 15 Jan 2004 15:18:59 -0600 [thread overview]
Message-ID: <uwu7sykos.fsf@isisSEND.vanderbiltME.eduSPAM> (raw)
In-Reply-To: <567ce618.0401151231.34be063f@posting.google.com>
On Thu, 15 Jan 2004, Randy Yates wrote:
> I've looked high, looked low, and I for the life of me can't
> find any documentation (in either gnus.pdf, message.pdf, apropos,
> and the menus) on how to save an attachment in an email to a file.
(info "(gnus)MIME Commands")
An attachment is really just a MIME part. The above page gives
two-key-long sequences, but when the cursor is on a MIME part button (the
thing in brackets), you don't need the K prefix key.
So in your case, pressing 'o' while the cursor is on the attachment button
would offer saving it to a file.
--
David Hanak - Research Engineer
Institute for Software Integrated Systems | http://www.isis.vanderbilt.edu
Vanderbilt University | Work phone: (615) 322-8472
Box 1829, Station B, Nasville, TN 37235 | PGP key ID: 266BC45F
prev parent reply other threads:[~2004-01-15 21:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-15 20:31 Randy Yates
2004-01-15 21:18 ` David Hanak [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=uwu7sykos.fsf@isisSEND.vanderbiltME.eduSPAM \
--to=dhanakdont@isissend.vanderbiltme.eduspam \
/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).