Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: gnus-summary-enter-digest-group
Date: 19 Feb 1999 22:36:04 +0100	[thread overview]
Message-ID: <m3pv76hy9n.fsf@quimbies.gnus.org> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "19 Feb 1999 19:39:33 +0100"

Kai.Grossjohann@CS.Uni-Dortmund.DE writes:

> Forwarded messages will always be shown as one message/rfc822 part
> containing a text/plain part, and users are always going to want to
> look at the latter.  The naming suggests to look at the former,
> though.

Well, nndoc does multiparts thusly:

   [  66: -> larsi@ifi.uio.no ] <* mixed> [Brian Gorka <gorkab@cyberpass.net>]
       [   2: -> larsi@ifi.uio.no ] <1 text>
       [  44: -> larsi@ifi.uio.no ] <2 rfc822>
           [  40: Brian Gorka         ] <2 text> S O m in a Summary Buffer
       [   4: -> larsi@ifi.uio.no ] <3 text>

The first article is the complete thing.  The second is the first text 
part.  The third is the complete rfc822 part (with the Mime headers,
which will usually just say something like "Content-Disposition:
inline").  The fourth is the contents of the rfc822 part.  The fifth
is the final text/plain part.

Seems logical to me.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen


  reply	other threads:[~1999-02-19 21:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-02-15 20:09 gnus-summary-enter-digest-group Jack Vinson
1999-02-19 16:10 ` gnus-summary-enter-digest-group Lars Magne Ingebrigtsen
1999-02-19 18:39   ` gnus-summary-enter-digest-group Kai.Grossjohann
1999-02-19 21:36     ` Lars Magne Ingebrigtsen [this message]
1999-02-20 12:03       ` gnus-summary-enter-digest-group Per Abrahamsen
1999-02-21 12:36       ` gnus-summary-enter-digest-group Kai.Grossjohann
1999-02-26  6:52         ` gnus-summary-enter-digest-group Lars Magne Ingebrigtsen
1999-02-26 15:37           ` gnus-summary-enter-digest-group Kai.Grossjohann

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=m3pv76hy9n.fsf@quimbies.gnus.org \
    --to=larsi@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).