Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: info-gnus-english@gnu.org
Subject: Re: Reading the article/message in elisp
Date: Thu, 13 Jul 2023 02:26:04 +0200	[thread overview]
Message-ID: <878rbkejxf.fsf@web.de> (raw)
In-Reply-To: <87edld781r.fsf@gmail.com>

Robert Pluim <rpluim@gmail.com> writes:

>     Husain>         (defun husain--test-message-subject-yank ()
>     Husain>           (interactive)
>     Husain>           (save-excursion
>     Husain>             (let ((subj (message-fetch-field "Subject")))
>     Husain>               (if subj
>     Husain>                   (message subj)
>     Husain>                 (gnus-summary-show-article)
>     Husain>                 (gnus-summary-select-article-buffer)
>     Husain>                 (message (message-fetch-field "Subject"))))))
>
>     Husain> this still doesn't work as intended because it does not
>     Husain> restore the window if the point is in a gnus-summary
>     Husain> buffer pointing to an article not open.
>
>     Husain> Is there a gnus function that can build the message in a
>     Husain> temp buffer?
>
> 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.

And you want to call `message' like (message "%s" ...) here, Husain:

When the ... can be arbitrary text, `message' will barf when the argument
accidentally contains %-sequences, like in

 (message "D'Oh, didn't expect a %-sequence here")


Michael.



  parent reply	other threads:[~2023-07-13  0:26 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
  -- strict thread matches above, loose matches on Subject: below --
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
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
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=878rbkejxf.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --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).