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
>
> So this works, in the sense that it stops me waiting forever... However,
> it seems (early days yet) that when it fails to open the connection to
> an NNTP server, it stops retrieving news and I have to hit 'g' again to
> get the counts etc. updated for other servers. But much better than
>
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
Eric S Fraga writes:
> On Sunday, 2 Jul 2023 at 16:59, Eric Abrahamsen wrote:
>> If everyone's hitting this with NNTP servers, you can set
>> `nntp-connection-timeout' to a number of seconds. It is nil by default,
>> which I guess would result in permanent hangs.
>
> So this works, in the sense
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!
On Sunday, 2 Jul 2023 at 16:59, Eric Abrahamsen wrote:
> If everyone's hitting this with NNTP servers, you can set
> `nntp-connection-timeout' to a number of seconds. It is nil by default,
> which I guess would result in permanent hangs.
So this works, in the sense that it stops me waiting
On Sunday, 2 Jul 2023 at 16:59, Eric Abrahamsen wrote:
> If everyone's hitting this with NNTP servers, you can set
> `nntp-connection-timeout' to a number of seconds. It is nil by default,
> which I guess would result in permanent hangs.
Thank you for the suggestion. I have set this to 15