From: "Dewey M. Sasser" <dewey@newvision.com>
Subject: automatically splitting incoming digests
Date: 25 Mar 1997 08:52:40 -0800 [thread overview]
Message-ID: <deweyg1xj52xz.fsf@aerosmith.newvision.com> (raw)
I've written some stuff to automatically split incoming digest
messages (only the ones you specify, of course) so that they can be
handled as individual messages by the normal nnmail-split-method.
(This allows me to save individual messages and score/thread without
having to respool each digest individually.)
Is there general interest in this feature? Should I make up an
addition patch for Lars to put into GNUS? Or is the response
"intelligent people use C-d to read digests. Forget it." :)
Dewey
PS -- feel free to send to me individually and I'll post a summary to
the list. That way we don't all pollute the list.
PPS -- a subject of "digest-split: yes" or "digest-split: no" would
be helpful if your answers are that clear cut.
--
Dewey M. Sasser voice: (617) 494-6000
dewey@newvision.com PGP Key from public servers
PGP mail preferred.
next reply other threads:[~1997-03-25 16:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-03-25 16:52 Dewey M. Sasser [this message]
1997-03-30 8:48 ` Lars Magne Ingebrigtsen
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=deweyg1xj52xz.fsf@aerosmith.newvision.com \
--to=dewey@newvision.com \
/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).