Adam Sjøgren 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
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 h
Adam Sjøgren 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
> messa
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 Sjøgren 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-
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!
