From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: Constantly having to use `^' for server buffer to close then open server
Date: Thu, 01 Oct 2020 11:08:56 -0700 [thread overview]
Message-ID: <87o8ll4y4n.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <871rihyhd6.fsf@tullinup.koldfront.dk>
Adam Sjøgren <asjo@koldfront.dk> writes:
> Eric writes:
>
>> I think this has been a perennial problem for all of us.
>
> Hm, I don't see this problem.
>
> I wonder if it is because I am network-wise close to the server
> (Denmark → Germany, I believe).
>
> Or because I've configured Gnus to check for news every 5 minutes when
> Emacs is idle (and I run an Emacs for Gnus only), so the connection is
> kept alive that way.
I would guess this is the answer. Kind of a manual, heavyweight
keepalive. My feeling is that, when the connection dies, I've usually
left it alone for ~10 minutes or more.
next prev parent reply other threads:[~2020-10-01 18:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-01 13:07 Harry Putnam
2020-10-01 15:06 ` Tim Landscheidt
2020-10-01 16:02 ` Eric Abrahamsen
2020-10-01 17:40 ` Adam Sjøgren
2020-10-01 18:08 ` Eric Abrahamsen [this message]
2020-10-01 18:22 ` Adam Sjøgren
2020-10-01 17:43 ` James Cloos
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=87o8ll4y4n.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).