From: ShengHuo ZHU <zsh@cs.rochester.edu>
Subject: Re: Suggestion for saving attachments
Date: 03 Nov 2000 01:08:57 -0500 [thread overview]
Message-ID: <2nvgu5y4cm.fsf@tiger.jia.vnet> (raw)
In-Reply-To: <m3hf6ak4al.fsf@mutzel.brumpf.de>
Christoph Conrad <christoph.conrad@gmx.de> writes:
> Hello ShengHuo,
>
> i read about the following functionality in another mail/newsreader
> (can't remember the name...).
>
> After saving an attachment the program optionally (by user-request)
> _replaces_ the attachment (or the content of the attachment) with the
> path to the saved attachment, something like:
>
> - Attachment initially saved to "/home/cc/docs/foobar.txt" -
>
> I think it would be fine to preserve the attachment itself, e.g. to
> replace the content of the attachment with this message.
>
> This is a functionality i think it's very useful, cause the user often
> does not want to have two places where an attachment is stored,
> especially in the case of really big attachments. Often i want to work
> with a document received in an attachment and don't want to preserve the
> original document, but want to know where i saved the original document
> initially.
The functionality has been implemented, though only one part each
time. To save and strip, press `C-o' on the MIME button, then an edit
buffer will show. If you are sure that Gnus has done the Right
Thing(TM), type `C-c C-c' to replace the part with a message/external-body.
Of course, now Gnus inlines message/external-body.
ShengHuo
next parent reply other threads:[~2000-11-03 6:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m3hf6ak4al.fsf@mutzel.brumpf.de>
2000-11-03 6:08 ` ShengHuo ZHU [this message]
2000-11-03 13:11 ` Christoph Conrad
2000-11-03 14:04 ` ShengHuo ZHU
2000-11-03 16:30 ` Christoph Conrad
2000-11-03 16:47 ` ShengHuo ZHU
2000-11-03 20:47 ` Christoph Conrad
2000-11-04 15:14 ` ShengHuo ZHU
2000-11-04 20:56 ` Christoph Conrad
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=2nvgu5y4cm.fsf@tiger.jia.vnet \
--to=zsh@cs.rochester.edu \
/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).