From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: auto open servers?
Date: Sat, 12 Feb 2022 13:31:19 -0800 [thread overview]
Message-ID: <87sfsn93h4.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87iltjvlgz.fsf@zoho.eu>
Emanuel Berg <moasenwood@zoho.eu> writes:
> Eric Abrahamsen wrote:
>
>> You can just put my code inside Emanuel's code:
>>
>> (defun gnus-reopen-servers ()
>> (interactive)
>> (unless (get-buffer gnus-server-buffer)
>> (gnus-group-enter-server-mode))
>> (dolist (elem gnus-opened-servers)
>> (gnus-close-server (car elem)))
>> (with-current-buffer gnus-server-buffer
>> (gnus-server-open-all-servers)))
>>
>> Then you'll want to either attach that to a hook, or put it
>> on a timer, or bind it to a key... or some combination
>> of those.
>
> Yeah, but why is it necessary to `gnus-close-server' at all?
In my experience (though this could be a misinterpretation), sometimes
when Gnus thinks an nntp server is already open it will continue to
treat it as open, even if the server has actually stopped responding.
So you get the timeouts as Gnus tries to talk to a dead server. Better
to explicitly close and re-open.
next prev parent reply other threads:[~2022-02-12 21:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-22 1:28 Emanuel Berg
2022-01-24 8:39 ` Alberto Luaces
2022-01-24 9:40 ` Emanuel Berg
2022-01-24 10:06 ` Emanuel Berg
2022-01-24 10:46 ` Andreas Schwab
2022-01-25 21:28 ` Emanuel Berg
2022-01-25 21:35 ` Emanuel Berg
2022-02-12 16:25 ` hput
2022-02-12 20:24 ` Eric Abrahamsen
2022-02-12 21:11 ` Emanuel Berg
2022-02-12 21:31 ` Eric Abrahamsen [this message]
2022-02-12 21:38 ` Emanuel Berg
2022-02-23 16:07 ` hput
2022-02-23 16:19 ` hput
2022-02-23 16:44 ` Eric Abrahamsen
2022-02-26 6:29 ` Emanuel Berg
2022-02-26 6:34 ` Emanuel Berg
2022-02-12 21:10 ` Emanuel Berg
2022-02-13 13:29 ` hput
2022-02-13 22:46 ` Emanuel Berg
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=87sfsn93h4.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=ding@gnus.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).