Re: new wifi connection = nntp timeout = Emacs restart?

[Eric Abrahamsen <eric@ericabrahamsen.net>]

David Engster <deng@randomsample.de> writes:

>> Andreas Schwab <schwab@linux-m68k.org> writes:
>>
>>> On Apr 17 2020, Gijs Hillenius wrote:
>>>
>>>> Yes, I do that too. And when I forget, I /have/ to quit Gnus when I wake
>>>> up the laptop, or else hitting g will make Gnus just hang out there for
>>>> a long time before it returns empty handed.
>>>
>>> Does it work to close the servers (gnus-close-all-servers)?
>>
>> I use "z" sort of compulsively, any time I haven't touched Gnus for a
>> while. (I've also put all my nntp groups at level 5 and all my nnimap
>> groups at level 3, so I can do "3 g" and not worry about it.)
>>
>> "z" usually works, but the point of this thread was that, when I switch
>> network connections, it often *doesn't*, and neither does restarting
>> Gnus. I've got to kill all of Emacs.
>
> This is weird.
>
> I see you're using current master. Does this also happen with current
> Emacs 27 pretest?

I haven't tried switching back to Emacs 27, but it's been happening for
ages, since master *was* 27, so I wouldn't expect much difference.

> I usually do not even close severs or suspend Gnus after a network
> switch. I just hit 'g', and if Gnus hangs I lean on Ctrl+g until it
> aborts and then hit 'g' again, which is usually enough to re-open the
> servers.

Yeah, that's basically just the long way around for closing all servers
:)

> I've already thought of using DBus to automate closing of servers on
> network change, but never bothered to actually do it because it works
> well enough...

It works well enough for me, too, until it doesn't :( Maybe I'll open a
bug report and see if anyone's got any hints about debugging, it's
fairly reproducible.

E