From: Ted Stern <stern@tera.com>
Cc: ding@gnus.org
Subject: Re: splitting digests (C-d)
Date: 21 Dec 1999 14:34:57 -0800 [thread overview]
Message-ID: <ycciu1rhqi6.fsf@orff.sea.tera.com> (raw)
In-Reply-To: Vladimir Volovich's message of "22 Dec 1999 01:04:49 +0300"
I can tell you the problem right off ... it is the message separator:
----------
There is an alist somewhere (nndoc-something-digest...) that has a list of
different digest types and how they are to be parsed. I get a digest that is
separated by equals signs rather than dashes and have the same problem as you.
I've tried adding to or modifying that variable but I must be missing
something because I can never get it to work.
--
Ted Stern Porting/Tuning/Analysis, Applications & Libraries
Tera Computer Company http://www.tera.com
411 First Avenue South, Suite 600 Direct 206/701-2182, Main 701-2000
Seattle, WA 98104-2860 Fax1 206/701-2205, Fax2 701-2500
prev parent reply other threads:[~1999-12-21 22:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-21 22:04 Vladimir Volovich
1999-12-21 22:34 ` Ted Stern [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=ycciu1rhqi6.fsf@orff.sea.tera.com \
--to=stern@tera.com \
--cc=ding@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).