* Getting Keywords: from parent article in message-setup-hook when following up
@ 2023-07-03 16:15 Adam Sjøgren
2023-07-03 16:38 ` Eric Abrahamsen
0 siblings, 1 reply; 6+ messages in thread
From: Adam Sjøgren @ 2023-07-03 16:15 UTC (permalink / raw)
To: info-gnus-english
How do I get hold of the parent articles' Keywords: in
message-setup-hook when I do a follow up?
I can get eg From: by lookin in message-reply-headers - but Keywords:
are not in there.
Is there a trick I can use?
Best regards,
Adam
--
"The laws of perspective have been repealed! Adam Sjøgren
Objects no longer diminish in size with distance!" asjo@koldfront.dk
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Getting Keywords: from parent article in message-setup-hook when following up
2023-07-03 16:15 Getting Keywords: from parent article in message-setup-hook when following up Adam Sjøgren
@ 2023-07-03 16:38 ` Eric Abrahamsen
2023-07-03 18:57 ` Adam Sjøgren
0 siblings, 1 reply; 6+ messages in thread
From: Eric Abrahamsen @ 2023-07-03 16:38 UTC (permalink / raw)
To: info-gnus-english
Adam Sjøgren <asjo@koldfront.dk> writes:
> How do I get hold of the parent articles' Keywords: in
> message-setup-hook when I do a follow up?
>
> I can get eg From: by lookin in message-reply-headers - but Keywords:
> are not in there.
>
> Is there a trick I can use?
I think the "big" solution is to visit `message-reply-buffer', if that's
a live buffer, and parse its contents.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Getting Keywords: from parent article in message-setup-hook when following up
2023-07-03 16:38 ` Eric Abrahamsen
@ 2023-07-03 18:57 ` Adam Sjøgren
2023-07-03 23:23 ` Eric Abrahamsen
0 siblings, 1 reply; 6+ messages in thread
From: Adam Sjøgren @ 2023-07-03 18:57 UTC (permalink / raw)
To: info-gnus-english
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.
Thanks!
Adam
--
'As usual, Bob Dylan said it best when he wrote in Adam Sjøgren
1965, "He not busy being born, is busy dying."' asjo@koldfront.dk
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Getting Keywords: from parent article in message-setup-hook when following up
2023-07-03 18:57 ` Adam Sjøgren
@ 2023-07-03 23:23 ` Eric Abrahamsen
2023-07-05 12:20 ` Adam Sjøgren
0 siblings, 1 reply; 6+ messages in thread
From: Eric Abrahamsen @ 2023-07-03 23:23 UTC (permalink / raw)
To: info-gnus-english
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...
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Getting Keywords: from parent article in message-setup-hook when following up
2023-07-03 23:23 ` Eric Abrahamsen
@ 2023-07-05 12:20 ` Adam Sjøgren
2023-07-05 16:48 ` Eric Abrahamsen
0 siblings, 1 reply; 6+ messages in thread
From: Adam Sjøgren @ 2023-07-05 12:20 UTC (permalink / raw)
To: info-gnus-english
Eric writes:
> 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...
Haha, yes, and if you take a couple of more steps back, all computing
is manipulation of global memory ;-)
But I think not having one hook storing the information and another
one using it will be a little less ugly, so thanks for the hint - the
naming of these variables is often not obvious to me.
Best regards,
Adam
--
"6666 - the devils neighbour" Adam Sjøgren
asjo@koldfront.dk
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Getting Keywords: from parent article in message-setup-hook when following up
2023-07-05 12:20 ` Adam Sjøgren
@ 2023-07-05 16:48 ` Eric Abrahamsen
0 siblings, 0 replies; 6+ messages in thread
From: Eric Abrahamsen @ 2023-07-05 16:48 UTC (permalink / raw)
To: info-gnus-english
Adam Sjøgren <asjo@koldfront.dk> writes:
> Eric writes:
>
>> 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...
>
> Haha, yes, and if you take a couple of more steps back, all computing
> is manipulation of global memory ;-)
>
> But I think not having one hook storing the information and another
> one using it will be a little less ugly, so thanks for the hint - the
> naming of these variables is often not obvious to me.
Ugh, don't get me started. What's the difference between
gnus-current-article and gnus-article-current? No one will ever know.
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2023-07-05 16:49 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-07-03 16:15 Getting Keywords: from parent article in message-setup-hook when following up 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
2023-07-05 12:20 ` Adam Sjøgren
2023-07-05 16:48 ` Eric Abrahamsen
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).