From: Husain Alshehhi <husain@alshehhi.io>
To: Robert Pluim <rpluim@gmail.com>
Cc: Husain Alshehhi <husain@alshehhi.io>, info-gnus-english@gnu.org
Subject: Re: Reading the article/message in elisp
Date: Fri, 14 Jul 2023 00:52:18 +0000 [thread overview]
Message-ID: <87jzv38gci.fsf@alshehhi.io> (raw)
Robert Pluim <rpluim@gmail.com> writes:
>
> In a temp buffer, no, but you can access the article buffer using eg
> `gnus-with-article' or `gnus-with-article-buffer', or even
> `gnus-with-article-headers' if you only care about the headers.
I suppose that gnus-with-article-buffer works, almost. In the case that
I am in gnus summary page, with the point on an unopened article, when I
run the following:
(defun husain--test-gnus-with-article-buffer()
(interactive)
(gnus-with-article-buffer
(message "%s" (message-fetch-field "Subject"))))
It fails to read the subject. However, it works very well after I open
the article. I think this solves 95% of the cases I run into.
Thank you.
next reply other threads:[~2023-07-14 0:52 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 0:52 Husain Alshehhi [this message]
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
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=87jzv38gci.fsf@alshehhi.io \
--to=husain@alshehhi.io \
--cc=info-gnus-english@gnu.org \
--cc=rpluim@gmail.com \
/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).