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

Excerpts from William Morgan's message of Wed Aug 19 14:55:03 -0400 2009:
> Reformatted excerpts from Kevin Riggle's message of 2009-08-18:
> > 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.
> 
> What I'm saying is that this hook will execute *after* each message is
> added to the index, so if Sup found several new messages, all except the
> first one will wait on this hook to execute before being added to the
> index. Or do you mean block in some sense besides "wait for completion"?

Oh, duh.  I take your point -- I've sent a new patch.

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