From: John Haman <mail@johnhaman.org>
To: ding@gnus.org
Subject: Re: Gnus refuses to connect after suspend and resume in different network, but Gnus in fresh emacs works
Date: Fri, 11 Aug 2023 17:26:09 -0400 [thread overview]
Message-ID: <m1edk9e0em.fsf@johnhaman.org> (raw)
In-Reply-To: <m11qg9z5g3.fsf@johnhaman.org>
John Haman <mail@johnhaman.org> writes:
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> Alberto Luaces <aluaces@udc.es> writes:
>>
>>> Steinar Bang <sb@dod.no> writes:
>>>
>>>> Has anyone else observed this behaviour?
>>>
>>> I think many.
>>>
>>>> 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.
>>>
>>> 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.
>>
>> I was going to say that I thought someone had added an option for
>> closing Gnus servers when a laptop sleeps -- I looked at the library and
>> it was me :(
>>
>> See if you've got a `gnus-dbus-close-on-sleep' option, and if so, try
>> setting it to t.
>>
>>
>
> Is there anything like this for MacOS? Windows?
Actually, just installing dbus from homebrew seems to remediate Gnus's suspend issues on MacOS.
--
Dr. John Haman
Maryland, USA
next prev parent reply other threads:[~2023-08-11 21:26 UTC|newest]
Thread overview: 11+ 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-08-11 20:31 ` John Haman
2023-08-11 21:26 ` John Haman [this message]
2023-01-30 19:31 ` Steinar Bang
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=m1edk9e0em.fsf@johnhaman.org \
--to=mail@johnhaman.org \
--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).