From: Steinar Bang <sb@dod.no>
To: ding@gnus.org
Subject: Re: Gnus refuses to connect after suspend and resume in different network, but Gnus in fresh emacs works
Date: Mon, 30 Jan 2023 20:31:47 +0100 [thread overview]
Message-ID: <87o7qf3jks.fsf@dod.no> (raw)
In-Reply-To: <87o7r4uog0.fsf@eps142.cdf.udc.es>
>>>>> Alberto Luaces <aluaces@udc.es>:
>> Does anyone know how to fix this (other than starting a new emacs)?
> You can start by closing all opened but stale server connections with
> "C" in the server buffer, and then reconnecting to everything (it
> implies reopening connections) with "g" in the group buffer.
Thanks! I will save this somewhere and try it next time this occurs.
> Some time ago I read that someone got this automated by catching the
> suspend dbus event and closing the connections either on suspending or
> resuming.
Oh, that would be nice!
prev parent reply other threads:[~2023-01-30 19:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-06 14:22 Steinar Bang
2023-01-12 8:50 ` Alberto Luaces
2023-01-12 21:42 ` Eric Abrahamsen
2023-01-13 7:55 ` Robert Pluim
2023-01-13 9:47 ` Alberto Luaces
2023-01-13 17:49 ` Eric Abrahamsen
2023-01-30 19:40 ` Steinar Bang
2023-01-30 20:48 ` Eric Abrahamsen
2023-01-30 19:31 ` Steinar Bang [this message]
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=87o7qf3jks.fsf@dod.no \
--to=sb@dod.no \
--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).