From: Shenghuo ZHU <zsh@cs.rochester.edu>
Subject: Re: Reading standard digests
Date: 03 Nov 1999 13:40:43 -0500 [thread overview]
Message-ID: <5bbt9bh104.fsf@brain.cs.rochester.edu> (raw)
In-Reply-To: Dick Knowles's message of "03 Nov 1999 13:15:54 -0500"
>>>>> "Dick" == Dick Knowles <knowles@averstar.com> writes:
[...]
Dick> I checked nndoc-article-type: in pgnus, it's mime-parts; in gnus
Dick> it's mime-digest. As an experiment, I stole the mime-digest
Dick> piece of nndoc-type-alist from gnus and added it to my running
Dick> pgnus, and also stole and loaded nndoc-mime-digest-type-p. When
Dick> I did this, the mime-digest (no longer mime-parts) worked as it
Dick> had in gnus. Articles had their own headers only, not the
Dick> digest headers followed by article headers; and the summary and
Dick> threading worked as before. So why was mime-digest removed? It
Dick> appears that mime-digest and mime-parts dismantle the digest
Dick> differently. What can I expect to break with my little
Dick> experiment, or can I safely make this change locally?
I don't know why Lars removed MIME-digest in February.
I guess it should be safe.
I think a customizable preference variable should be added, since Gnus
users are always picky.
Dick> In case this helps explain anything, here are the headers and a bit
Dick> more from one of the digests I'm getting:
Dick> X-From-Line: PERRY-D-request@rootsweb.com Wed Nov 3 00:48 EST 1999
Dick> Received: from [...]
Dick> From: PERRY-D-request@rootsweb.com
Dick> Date: Tue, 2 Nov 1999 21:46:37 -0800 (PST)
Dick> X-Gnus-Mail-Source: file:/var/mail/knowles
Dick> Message-Id: <199911030546.VAA16738@bl-14.rootsweb.com>
Dick> Subject: PERRY-D Digest V99 #235
Dick> X-Loop: PERRY-D@rootsweb.com
Dick> X-Mailing-List: <PERRY-D@rootsweb.com> archive/volume99/235
Dick> Precedence: list
Dick> MIME-Version: 1.0
Dick> To: PERRY-D@rootsweb.com
Dick> Reply-To: PERRY-L@rootsweb.com
Dick> Content-Type: multipart/digest; boundary="----------------------------"
Dick> X-Content-Length: 3367
Dick> Lines: 113
Dick> Xref: mesmer.i2ada mail.roots:1029
[...]
multipart/digest help a lot. While, in some digests
multipart/mixed+message/rfc822 is used instead, such as
comp.sys.mac.digest.
--
Shenghuo ZHU
next prev parent reply other threads:[~1999-11-03 18:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-02 22:33 Dick Knowles
1999-11-03 15:56 ` Shenghuo ZHU
1999-11-03 18:15 ` Dick Knowles
1999-11-03 18:40 ` Shenghuo ZHU [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-10-27 20:35 reading " Dick Knowles
1999-11-07 0:10 ` Lars Magne Ingebrigtsen
1999-11-08 17:15 ` Dick Knowles
1999-11-11 6:26 ` Lars Magne Ingebrigtsen
1999-11-11 21:54 ` Dick Knowles
1999-11-15 20:44 ` Lars Magne Ingebrigtsen
1999-11-15 22:54 ` Dick Knowles
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=5bbt9bh104.fsf@brain.cs.rochester.edu \
--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).