From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: New Digest Handling?
Date: 12 Jun 1999 04:16:34 +0200 [thread overview]
Message-ID: <m3btem9n99.fsf@quimbies.gnus.org> (raw)
In-Reply-To: davidbe@msil.sps.mot.com's message of "20 Apr 1999 09:40:34 +0200"
davidbe@msil.sps.mot.com (E. David Bell) writes:
> Is digest splitting being handled differently now? I do a
> gnus-summary-read-document on a digest and get:
>
> [Informal Aliyah ] 19-Apr <* mixed> TACHLIS digest 1734
> [Informal Aliyah ] 19-Apr <1 text>
This is how nndoc handles MIME digests.
> Any way around this?
You can specify `nndoc-article-type' as `slack-digest', or something.
Although how you would do that I don't quite know. :-)
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~1999-06-12 2:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-20 7:40 E. David Bell
1999-04-20 14:29 ` Jack Vinson
1999-04-21 3:09 ` Tony E. Bennett
1999-06-12 2:16 ` Lars Magne Ingebrigtsen [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=m3btem9n99.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).