From: Emanuel Berg <incal@dataswamp.org>
To: info-gnus-english@gnu.org
Subject: Re: Reading the article/message in elisp
Date: Sun, 16 Jul 2023 17:35:03 +0200 [thread overview]
Message-ID: <87o7kbhntk.fsf@dataswamp.org> (raw)
In-Reply-To: <87mszwwp82.fsf@web.de>
Michael Heerdegen wrote:
>>>> The function `mail-header-subject' works but then you
>>>> don't get to select the header.
>>>
>>> What does "you don't get to select the header" mean?
>>
>> You only get the Subject header.
>
> With this accessor function, yes. And with the others, you
> get the other struct fields. Not sure what your question is.
We would like an arbitrary header access function where the
header is provided as an argument, as in
(defun gnus-article-header-value (hdr)
"Get the value of HDR for the current article."
(with-current-buffer gnus-original-article-buffer
(gnus-fetch-field hdr) ))
only one that works from anywhere, where the article is
fetched from what article is selected (or, lacking that, where
the point is) in the summary buffer.
--
underground experts united
https://dataswamp.org/~incal
next prev parent reply other threads:[~2023-07-16 15:35 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 0:52 Husain Alshehhi
2023-07-14 1:07 ` Emanuel Berg
2023-07-14 1:48 ` Michael Heerdegen
2023-07-14 4:18 ` Emanuel Berg
2023-07-14 5:11 ` Michael Heerdegen
2023-07-14 5:17 ` Emanuel Berg
2023-07-15 3:56 ` Michael Heerdegen
2023-07-15 4:57 ` Emanuel Berg
2023-07-15 5:12 ` Michael Heerdegen
2023-07-15 5:28 ` Emanuel Berg
2023-07-16 2:43 ` Michael Heerdegen
2023-07-16 15:35 ` Emanuel Berg [this message]
2023-07-29 3:24 ` Michael Heerdegen
2023-07-15 6:45 ` Emanuel Berg
2023-07-16 2:40 ` Michael Heerdegen
2023-07-16 15:38 ` Emanuel Berg
-- strict thread matches above, loose matches on Subject: below --
2023-07-12 4:59 Husain Alshehhi
2023-07-12 10:12 ` Robert Pluim
2023-07-13 0:04 ` Emanuel Berg
2023-07-13 0:26 ` Michael Heerdegen
2023-07-11 3:33 husain
2023-07-11 11:29 ` Emanuel Berg
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=87o7kbhntk.fsf@dataswamp.org \
--to=incal@dataswamp.org \
--cc=info-gnus-english@gnu.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).