From: Rich Lane <rlane@club.cc.cmu.edu>
To: Tero Tilus <tero@tilus.net>
Cc: Sup users <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] best method for before-add-message.rb
Date: Sun, 13 Feb 2011 12:45:04 -0500 [thread overview]
Message-ID: <1297618949-sup-445@zyrg.net> (raw)
In-Reply-To: <1297589599-sup-596@tilus.net>
Excerpts from Tero Tilus's message of 2011-02-13 04:51:02 -0500:
> Moritz Wilhelmy, 2011-02-13 03:34:
> > Can I pull arbitrary, parsed headers directly out of the message
> > object, or do I have to do my own parsing?
>
> Uh, oh. Looks like no, but it is pretty close, berause
> Message#parse_header already builds parsed hash of arbitrary headers
> internally.
>
I use "hs = message.source.load_header(message.source_info)", which we
should probably make a convenience method on Message.
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2011-02-13 18:49 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
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 ` Rich Lane [this message]
2011-02-13 17:12 ` [sup-talk] best method for before-add-message.rb 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=1297618949-sup-445@zyrg.net \
--to=rlane@club.cc.cmu.edu \
--cc=sup-talk@rubyforge.org \
--cc=tero@tilus.net \
/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