Gnus development mailing list
 help / color / mirror / Atom feed
From: SL Baur <steve@xemacs.org>
Subject: Re: Digest bursting
Date: 01 Nov 1997 19:44:26 -0800	[thread overview]
Message-ID: <m2affo3qp1.fsf@altair.xemacs.org> (raw)
In-Reply-To: wmperry@aventail.com's message of "01 Nov 1997 18:34:12 -0800"

William M Perry <wmperry@aventail.com> writes:

> Hrvoje Niksic <hniksic@srce.hr> writes:

>> Will Gnus support digest bursting in the future?  Does anyone else
>> think it might be useful?

>   You should be able to hit 'C-d' in the summary buffer and be put into the 
> equivalent of a 'virtual folder' in VM-speak.  Then you can select the
> articles and Br (respool) them to 'nnml'.

As far as I know, that code has always worked pretty good.

If you use procmail, you can have it burst digests for you.  Here's a
couple of recipes I've been using for some time now:

# Risks Digest
:0
* ^Return-Path:.*((owner-)?risks(-owner)?|risko)@
* ^Subject:[    ]*RISKS DIGEST
{
	:0c:
	risks-digest.spool

	# Split the digest, since digests suck
	:0f:risks.spool.lock
	| formail -ds >> risks.spool

	:0
	/dev/null
}

# cola via email
:0
* ^(Sender|Return-Path):.*owner-[lL]inux-[Aa]nnounce@
{
	:0c:
	lnx-announce-digest.spool

	# Now attempt splitting the digest
	:0f:linux-announce.spool.lock
	| formail -ds >> linux-announce.spool

	:0
	/dev/null
}


  reply	other threads:[~1997-11-02  3:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-11-01 19:54 Hrvoje Niksic
1997-11-02  2:34 ` William M. Perry
1997-11-02  3:44   ` SL Baur [this message]
1997-11-02 16:53   ` Hrvoje Niksic
1997-11-05 20:54     ` Lars Magne Ingebrigtsen
1997-11-03 14:00 Brian Gorka

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=m2affo3qp1.fsf@altair.xemacs.org \
    --to=steve@xemacs.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).