From: Hamish D <dmishd@gmail.com>
To: Philippe LeCavalier <support@plecavalier.com>
Cc: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] New User Hooks Details
Date: Thu, 3 Feb 2011 23:48:56 +0000 [thread overview]
Message-ID: <AANLkTinhwyCC46MgNN0OrGL4KRysmqajPMhkWjo3UMKz@mail.gmail.com> (raw)
In-Reply-To: <1296746458-sup-2021@plc.intranet.plecavalier.com>
> One bit of info that seems odd to me is when I issue 'sup -l' the hooks listed are nowhere to be found in the hooks folder yet they appear to be working. Is that normal?
sup -l will list the hooks you can use - it doesn't check what hooks
you've actually created.
> sample hook:
> #Mark Lists <lists>
> addressfile = File.open("/home/plecavalier/.sup/hooks/label.lists","r")
> if ! addressfile.grep(/#{message.list_address}/).empty?
> message.add_label :lists
> end
You can stick debug statements in - say:
debug "list address is #{message.list_address.inspect}, type is
#{message.list_address.class.to_s}"
and then see it in the log (while using sup, press ";" and scroll down
to the log buffer).
I think that message.list_address is actually of class Person, so you
would want to use message.list_address.email for your case. I've
updated the wiki to correct that - I think I may have written the
wrong information into the wiki to start with :/ so sorry for the
mistake.
Hamish
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2011-02-04 0:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-03 15:58 Philippe LeCavalier
2011-02-03 23:01 ` Tero Tilus
2011-02-03 23:48 ` Hamish D [this message]
2011-02-04 1:28 ` Antono Vasiljev
2011-02-05 2:15 ` Philippe LeCavalier
2011-02-05 2:54 ` Blake Sweeney
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=AANLkTinhwyCC46MgNN0OrGL4KRysmqajPMhkWjo3UMKz@mail.gmail.com \
--to=dmishd@gmail.com \
--cc=sup-talk@rubyforge.org \
--cc=support@plecavalier.com \
/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