From: Ted Zlatanov <tzz@lifelogs.com>
To: info-gnus-english@gnu.org
Subject: Re: Suppressing unavailable imap server by default
Date: Thu, 22 Sep 2016 08:19:36 -0400 [thread overview]
Message-ID: <8737kscejr.fsf@lifelogs.com> (raw)
In-Reply-To: <mailman.2746.1474467763.22741.info-gnus-english@gnu.org>
On Wed, 21 Sep 2016 15:48:58 +0200 Michael Albinus <michael.albinus@gmx.de> wrote:
MA> How could I change my configuration, that this timeout is reduced? Or
MA> that prior to connecting the server via imap there is a check, whether
MA> the server is reachable?
MA> Extra bonus if I could configure it such a way that I don't need to
MA> confirm that the server isn't reachable.
On Thu, 22 Sep 2016 10:25:26 +0800 Eric Abrahamsen <eric@ericabrahamsen.net> wrote:
EA> What I think would be preferable would be if a server status of "closed"
EA> persisted between Gnus restarts. Then you could just leave it closed,
EA> and open it manually when you decide you want to check news.
Manual work always sucks :)
I think a new server parameter `check-reachable' or something like that
would make sense. It could be a number (indicating connection timeout
time) or a path (a command to run to check connectivity).
I'll follow up on emacs-devel regarding socket timeouts in general. I
think the improvement has to be made in the C core.
Ted
next parent reply other threads:[~2016-09-22 12:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.2746.1474467763.22741.info-gnus-english@gnu.org>
2016-09-22 12:19 ` Ted Zlatanov [this message]
2016-09-22 13:27 ` Michael Albinus
[not found] ` <mailman.2819.1474550834.22741.info-gnus-english@gnu.org>
2016-09-22 13:31 ` Ted Zlatanov
2016-10-21 9:56 ` Michael Albinus
2016-09-21 13:48 Michael Albinus
2016-09-22 2:25 ` Eric Abrahamsen
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=8737kscejr.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=info-gnus-english@gnu.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).