From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: info-gnus-english@gnu.org
Subject: Re: Getting Keywords: from parent article in message-setup-hook when following up
Date: Mon, 03 Jul 2023 16:23:59 -0700 [thread overview]
Message-ID: <873524fuk0.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <877crgbz6b.fsf@tullinup.koldfront.dk>
Adam Sjøgren <asjo@koldfront.dk> writes:
> Eric writes:
>
>> I think the "big" solution is to visit `message-reply-buffer', if that's
>> a live buffer, and parse its contents.
>
> That sounds better than the ugly hack I have now, where I update a
> global variable from gnus-article-prepare-hook and use it in
> message-setup-hook - eeek.
When you think about it, updating a global variable is all the Gnus code
is doing! But better to rely on someone else's ugly hack, I suppose...
next prev parent reply other threads:[~2023-07-03 23:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 16:15 Adam Sjøgren
2023-07-03 16:38 ` Eric Abrahamsen
2023-07-03 18:57 ` Adam Sjøgren
2023-07-03 23:23 ` Eric Abrahamsen [this message]
2023-07-05 12:20 ` Adam Sjøgren
2023-07-05 16:48 ` Eric Abrahamsen
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=873524fuk0.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--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).