From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: Chris Richards <cjr@netpliance.net>, ding@gnus.org
Subject: Re: Excessively Painful Forwards
Date: 10 Apr 2000 09:52:54 +0200 [thread overview]
Message-ID: <vaf66tqgzop.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: Greg Stark's message of "09 Apr 2000 23:08:18 -0400"
Greg Stark <gsstark@mit.edu> writes:
> It might be tricky but basically what gnus needs is an option to provide to
> the backend that would be a closure to call when the operation was finished.
> Then the backend could schedule all its work and return immediately. Taking
> care of the processing of data in callbacks, calling the closure when it's
> finished.
Note that this is not quite sufficient for, eg, mail splitting. Here,
you get a large ~/Mail/Incoming file and there is no natural division
between chunks of work, like in process filters, so what it comes down
to is that you have to do that yourself.
And that's all I had been trying to say. Maybe `very hard' was an
exaggeration, but, well...
kai
--
The birch trees flay way too low these days.
prev parent reply other threads:[~2000-04-10 7:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-16 18:20 Chris Richards
2000-02-16 22:13 ` Kai Großjohann
2000-04-10 3:08 ` Greg Stark
2000-04-10 7:52 ` Kai Großjohann [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=vaf66tqgzop.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--cc=cjr@netpliance.net \
--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).