From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: <ding@gnus.org>
Subject: Re: C-c C-f and MIME
Date: Wed, 15 Aug 2001 19:51:28 +0200 [thread overview]
Message-ID: <vafzo91i53z.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <iluy9olcm9d.fsf@barbar.josefsson.org> (Simon Josefsson's message of "Wed, 15 Aug 2001 18:37:34 +0200")
Simon Josefsson <jas@extundo.com> writes:
> No, with ARG 4 I see multipart MIME headers. What I would want would
> be to decode and inline all MIME parts and then forward it. Much like
> taking the content of *Article* buffer and forwarding that.
Ah. So, `m M-> M-x insert-buffer RET *Article* RET' does what you
want?
kai
--
~/.signature: No such file or directory
next prev parent reply other threads:[~2001-08-15 17:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-15 13:17 Simon Josefsson
2001-08-15 14:57 ` Kai Großjohann
2001-08-15 16:37 ` Simon Josefsson
2001-08-15 17:51 ` Kai Großjohann [this message]
2001-08-15 18:11 ` Simon Josefsson
2001-08-15 15:03 ` Stainless Steel Rat
2001-08-15 17:30 ` ShengHuo ZHU
2001-08-15 18:21 ` Simon Josefsson
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=vafzo91i53z.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--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).