From mboxrd@z Thu Jan  1 00:00:00 1970
From: kevinr@free-dissociation.com (Kevin Riggle)
Date: Tue, 18 Aug 2009 19:36:15 -0400
Subject: [sup-talk] [PATCH] Add an after-add-message hook
In-Reply-To: <1250618123-sup-8797@masanjin.net>
References: <1250459229-4500-1-git-send-email-kevinr@free-dissociation.com>
	<1250618123-sup-8797@masanjin.net>
Message-ID: <1250638381-sup-2952@black-opal.mit.edu>

Excerpts from William Morgan's message of Tue Aug 18 13:56:15 -0400 2009:
> Reformatted excerpts from Kevin Riggle's message of 2009-08-16:
> > I want to do some unrelated processing on each message I receive, but
> > I don't want to block the message being added to the index.  This
> > patch adds a hook which runs /after/ the message is added to the
> > index.
> 
> Won't this block subsequent emails from being added to the index, when
> Sup gets multiple new emails during a poll?

I don't /think/ so, unless I misunderstand the way hooks work.  I assumed
the hook would execute and then execution of the loop would resume, and
I don't think I throw anything in the hook which should cause that either.

- Kevin
-- 
Kevin Riggle (kevinr at free-dissociation.com) 
http://free-dissociation.com