From: dsg@mitre.org (David S. Goldberg)
Cc: Robert Bihlmeyer <e9426626@stud2.tuwien.ac.at>, ding@gnus.org
Subject: Re: replying to mime parts
Date: 13 Jan 1998 11:05:49 -0500 [thread overview]
Message-ID: <m1b67nojr4y.fsf@blackbird.mitre.org> (raw)
In-Reply-To: Kai Grossjohann's message of "13 Jan 1998 15:11:01 +0100"
Rather than hack tm, I just use C-d (gnus-summary-enter-digest-group),
which splits out the message/rfc-822 (and other common forward
formats, as well as digests) into a group of its own and then reply,
followup etc from there. Works like a champ.
--
Dave Goldberg
Post: The Mitre Corporation\MS B305\202 Burlington Rd.\Bedford, MA 01730
Phone: 781-271-3887
Email: dsg@mitre.org
prev parent reply other threads:[~1998-01-13 16:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-01-13 13:43 Robert Bihlmeyer
1998-01-13 14:11 ` Kai Grossjohann
1998-01-13 16:05 ` David S. Goldberg [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=m1b67nojr4y.fsf@blackbird.mitre.org \
--to=dsg@mitre.org \
--cc=ding@gnus.org \
--cc=e9426626@stud2.tuwien.ac.at \
/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).