From: Philippe LeCavalier <support@plecavalier.com>
To: Philippe LeCavalier <support@plecavalier.com>
Cc: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] best method for before-add-message.rb
Date: Thu, 10 Feb 2011 17:09:11 -0500 [thread overview]
Message-ID: <1297375381-sup-2823@plc.intranet.plecavalier.com> (raw)
In-Reply-To: <1297364797-sup-8388@plc.intranet.plecavalier.com>
Hi All.
Excerpts from Philippe LeCavalier's message of Thu Feb 10 14:19:49 -0500 2011:
> Hi. I apologize in advance for the broken thread...Since I forgot a linebreak at the beginning of the body so everything got mangled upon exiting vim. I did my best to re-create the order.
>
>
> Excerpts from Mark Alexander's message of Thu Feb 10 12:00:17 -0500 2011:
>
> > Excerpts from Philippe LeCavalier's message of Thu Feb 10 11:52:53 -0500 2011:
>
> > > Hi Mark.
> > > Have you tried?
> > > > > case message.subj
> > > when /\[P4 SUBMIT/
> > > message.add_label :p4
> > > message.remove_label :inbox
> > > end
> > > No, I haven't tried remove_label.
>
> I did some testing and for some reason I cannot see, the above code automatically archives the msg without any obvious code telling sup to do so.
>
> If I:
>
> case message.from.email
> when /@plecavalier.com/
> message.add_label :TEST
> message.add_label :TEST2
> message.add_label :TEST3
> end
>
> tests sent to myself are respectively labeled TEST TEST2 TEST3 but are also striped of the inbox label. Since this is exactly what I want this works for me but...
Well, I don't know if this was the most efficient method but I took Mark's example and ran with it. This method accomplishes my goal to add(and remove!) multiple labels in one swish and is legible enough for the simple-minded like myself.
Note: the above statement re. removing the inbox label without having specifying it explicitely is false...No idea why Sup was doing that but restarting sup completely, fixed that oddity. Perhaps my understanding of 'H' is incorrect!?
Thanks a bunch Mark my inbox is well on it's way to 0 as it once was.
--
Thanks,
Phil
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2011-02-10 22:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-10 14:44 Philippe LeCavalier
2011-02-10 16:40 ` Mark Alexander
[not found] ` <1297356327-sup-9107@plc.intranet.plecavalier.com>
[not found] ` <1297357197-sup-5893@bloovis.org>
2011-02-10 19:19 ` Philippe LeCavalier
2011-02-10 22:09 ` Philippe LeCavalier [this message]
2011-02-13 1:34 ` Moritz Wilhelmy
2011-02-13 9:51 ` Tero Tilus
2011-02-13 13:00 ` [sup-talk] How to treat List-Id headers (Was: best method for before-add-message.rb) Moritz Wilhelmy
2011-02-13 17:45 ` [sup-talk] best method for before-add-message.rb Rich Lane
2011-02-13 17:12 ` Hamish D
2011-02-13 18:08 ` Philippe LeCavalier
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=1297375381-sup-2823@plc.intranet.plecavalier.com \
--to=support@plecavalier.com \
--cc=sup-talk@rubyforge.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