From: Stephen Berman <stephen.berman@gmx.net>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: info-gnus-english@gnu.org
Subject: Re: Gnus fetch freezes emacs
Date: Tue, 04 Jul 2023 13:31:15 +0200 [thread overview]
Message-ID: <87wmzfx69o.fsf@gmx.net> (raw)
In-Reply-To: <87zg4dq7ed.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Mon, 03 Jul 2023 09:36:26 -0700")
On Mon, 03 Jul 2023 09:36:26 -0700 Eric Abrahamsen <eric@ericabrahamsen.net> wrote:
> Eric S Fraga <e.fraga@ucl.ac.uk> 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.
Is this variable supposed to be set in the value of gnus-select-method?
For example, like this:
(setq gnus-select-method '(nntp "news.gmane.io"
(nntp-connection-timeout 3)))
>> 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. [...]
That sounds basically like what the function I'm using in place of
gnus-group-get-new-news (see my first post in this thread) does. Could
such a function take effect if added to one of the server hook variables
nntp-server-opened-hook, nntp-server-action-alist or
nntp-open-connection-function? From the descriptions in the manual it
isn't clear to me. Or is there some better Gnus hook variable for this
purpose? If not could one be added?
> Yeah, I'd put in a dumb fix for this that turned out to be buggy, so we
> just recently reverted it. I have a more thorough fix in progress
> somewhere here, that would report a server connection failure without
> interrupting the rest of the servers, but it's not done yet. I've had
> very little time for coding recently, but will get to it At Some Point.
>
> Glad it's at least better than it was. I wonder if we should have some
> generous timeout set by default...
It might make sense to continue this discussion in bug#52735.
Steve Berman
next prev parent reply other threads:[~2023-07-04 11:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-30 14:33 Prashant Tak
2023-06-30 19:33 ` Stephen Berman
2023-07-01 10:41 ` Eric S Fraga
2023-07-01 18:00 ` Stephen Berman
2023-07-02 15:15 ` Prashant Tak
2023-07-02 23:59 ` Eric Abrahamsen
2023-07-03 12:15 ` Eric S Fraga
2023-07-03 12:58 ` Eric S Fraga
2023-07-03 16:36 ` Eric Abrahamsen
2023-07-04 11:31 ` Stephen Berman [this message]
2023-07-04 17:02 ` Eric Abrahamsen
2023-07-04 19:55 ` Stephen Berman
2023-07-05 3:50 ` Eric Abrahamsen
2023-07-05 8:04 ` Stephen Berman
2023-07-05 18:55 ` Eric Abrahamsen
2023-07-05 20:09 ` Stephen Berman
2023-07-05 20:34 ` Eric Abrahamsen
2023-07-05 21:05 ` Stephen Berman
2023-07-03 19:22 ` Bob Newell
2023-07-04 8:13 ` Robert Pluim
2023-07-05 16:56 ` Gmail slowness/occasional SMTP hang Bob Newell
2023-07-02 17:37 ` Gnus fetch freezes emacs yeti
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=87wmzfx69o.fsf@gmx.net \
--to=stephen.berman@gmx.net \
--cc=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).