From: marcus-sup@quintic.co.uk (Marcus Williams)
Subject: [sup-talk] [PATCH] New hook (enabling message filters)
Date: Fri, 19 Oct 2007 11:52:31 +0100 [thread overview]
Message-ID: <47188C6F.30008@quintic.co.uk> (raw)
Hi -
Attached is a patch to poll.rb to add the ability to filter messages
pre-indexing. Theres one current problem with it which I cant figure out
and thats the warnings you get when its run from sup-sync about missing
a say_id - I think this is something to do with not having a buffer
manager in sup-sync. Anyone any ideas how to get the say method in
hooks.rb to fail gracefully to something else if the buffermanager isnt
available?
This hook allows you to do this in your .sup/hooks/before-add-message.rb:
##
if message.subj =~ /^\[sup-talk\]/
message.add_label "sup"
message.add_label "list"
end
message.add_label "work" if message.from =~ /mywork at email.com/
message.add_label "home" if message.from =~ /myhome at email.com/
##
.... and then when polling or during sup-sync this hook gets run for
every message it adds to the index. "message" is the about-to-be-indexed
email, changes made to it get passed on into the index.
Any comments or fixes (like the "say" issue), mail me (or reply on list)
Marcus
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: filter-hook.diff
Url: http://rubyforge.org/pipermail/sup-talk/attachments/20071019/4144dbc4/attachment.pl
next reply other threads:[~2007-10-19 10:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-19 10:52 Marcus Williams [this message]
2007-10-19 12:51 ` David Stubbs
[not found] ` <4d4780f700181787@IMSS-WIN>
2007-10-19 13:46 ` Marcus Williams
[not found] ` <4d6e9e1600182d59@IMSS-WIN>
2007-10-19 13:50 ` Marcus Williams
2007-10-19 14:03 ` David Stubbs
[not found] ` <4d7f58120018376f@IMSS-WIN>
2007-10-19 14:18 ` Marcus Williams
2007-10-19 14:21 ` David Stubbs
2007-11-05 2:40 ` William Morgan
2007-11-05 15:03 ` Marcus Williams
2007-11-05 15:38 ` William Morgan
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=47188C6F.30008@quintic.co.uk \
--to=marcus-sup@quintic.co.uk \
/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