From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Fetching Article Headers
Date: Sun, 27 Apr 2003 05:40:00 +0200 [thread overview]
Message-ID: <m3n0ictxpr.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <wwmof2uhwn3.fsf@tarc.net> (Taso N. Devetzis's message of "Fri, 25 Apr 2003 20:31:44 -0500")
"Taso N. Devetzis" <devetzis@snet.net> writes:
> 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).
Yes. If you wish to look at the actual article headers, you have to
fetch them. This is either done by setting *-nov-is-evil, or by
letting Gnus select the article.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~2003-04-27 3:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-26 1:31 Taso N. Devetzis
2003-04-27 3:40 ` Lars Magne Ingebrigtsen [this message]
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=m3n0ictxpr.fsf@quimbies.gnus.org \
--to=larsi@gnus.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;
as well as URLs for NNTP newsgroup(s).