Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: C-d displays duplicated parts
Date: 28 Aug 1999 00:11:42 +0200	[thread overview]
Message-ID: <m3lnawyiu9.fsf@quimbies.gnus.org> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "27 Aug 1999 23:51:47 +0200"

[-- Attachment #1: Type: text/plain, Size: 299 bytes --]

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> I must admit that I still don't understand why you need to introduce
> more parts.

   [ 168: Stephen J. Turnbull ] <* mixed> forwarded message
       [   7: Stephen J. Turnbull ] <1 text>
       [  23: Stephen J. Turnbull ] <2 rfc822>

[-- Attachment #2: Type: text/plain, Size: 619 bytes --]

           [   9: Stephen J. Turnbull ] <2 text> 日光"日光"

It's necessary if you want to treat all parts equally.  For instance,
here you have a multipart/mixed with one text/plain part and one
message/rfc822.  If you select the parts on the second "level", you
get articles that have headers from the parent.  The last article here
has headers from the rfc822 part itself.  And so on.

Not doing it this way would raise the contents of the rfc822 part "up"
one level, above where it properly belongs.

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

  parent reply	other threads:[~1999-08-27 22:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-07-20 19:55 Vladimir Volovich
1999-07-21  1:59 ` Justin Sheehy
1999-07-21  7:44   ` Vladimir Volovich
1999-08-27 21:05     ` Lars Magne Ingebrigtsen
1999-08-27 21:29       ` François Pinard
1999-08-27 21:51         ` Kai Großjohann
1999-08-27 22:04           ` Kai Großjohann
1999-08-27 22:11           ` Lars Magne Ingebrigtsen [this message]
1999-08-27 22:16             ` Kai Großjohann
1999-08-27 22:31               ` Lars Magne Ingebrigtsen
1999-08-28 13:53                 ` Kai Großjohann
1999-08-28 16:06                   ` François Pinard

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=m3lnawyiu9.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).