From: "Taso N. Devetzis" <devetzis@snet.net>
Subject: Fetching Article Headers
Date: Fri, 25 Apr 2003 20:31:44 -0500 [thread overview]
Message-ID: <wwmof2uhwn3.fsf@tarc.net> (raw)
Greetings,
I have written some hooks to snarf and examine article headers (for
mail back-ends -- I am using nnml if it matters), but I have a couple
of questions regarding the available functions and their behaviour.
I can find the headers easily enough as follows:
(defun blat-find-header (hdr)
(gnus-with-article-headers
(message-fetch-field hdr)))
This function, however, requires the headers in question to be visible
(since it uses *gnus-article-buffer*, I presume). I have had similar
results with manually (or using some of the built-ins) searching via
*gnus-parse-headers-hook* (wrong concept altogether on my part) and
*nnmail-prepare-incoming-header-hook* (same deal). The hooks and
functions (such as the *gnus-with-article-headers* macro) that rely on
the article buffer will also not work unless the article is selected
(and *gnus-article-buffer* is therefore current).
*gnus-alter-header-function* seems promising, but I am not convinced
that this is its Intended Purpose.
I know enough about gnus to be a danger to myself and others, so I
would ask your indulgence in pointing me in the right direction to
examine (all of) the article headers (for mail back-ends), regardless
of whether or not the article is selected (you know, cruise through
them in Summary mode). I understand that I may have to manually
select the article and parse the headers, but I want to make sure I am
not missing an obvious hook. Nothing in the docs springs out at me.
Thanks.
/taso
next reply other threads:[~2003-04-26 1:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-26 1:31 Taso N. Devetzis [this message]
2003-04-27 3:40 ` Lars Magne Ingebrigtsen
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=wwmof2uhwn3.fsf@tarc.net \
--to=devetzis@snet.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;
as well as URLs for NNTP newsgroup(s).