From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 47478@debbugs.gnu.org
Subject: bug#47478: 28.0.50; Provide customization option for nnimap-keepalive-timer
Date: Sun, 02 May 2021 09:57:19 -0700 [thread overview]
Message-ID: <87im41ul8w.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87a6pdmxv1.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sun, 02 May 2021 08:52:02 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> Bob Newell requested the ability to customize the
>> `nnimap-keepalive-timer', and I've opened this bug report with a patch
>> that adds a new `nnimap-keepalive-times' customization option.
>>
>> It lets you customize both function interval and period of inactivity,
>> or you can set it to nil to disable the keepalive altogether.
>
> Sure; makes sense.
Cool. In the meantime I've come to prefer the name
`nnimap-keepalive-intervals', if that's all right.
I'll add this to the manual, as well. Do you think it should be a
defvoo, or a regular customization option?
>> I also sneaked in a little extra change: since we provided the option to
>> use Dbus to close Gnus servers when your machine is going to sleep, I've
>> noticed that sometimes (more often than you'd think) I seem to be
>> sleeping the machine in between sending the keepalive NOOP and receiving
>> the response.
>
> I think that should be OK -- when we're looking for responses, we use
> tags, so the response from the NOOP shouldn't confuse anything.
> (Hopefully.)
Hopefully!
next prev parent reply other threads:[~2021-05-02 16:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-29 16:22 bug#47478: 28.0.50; Provide customization option for nnimap-keepalive-timer Eric Abrahamsen
2021-04-28 23:08 ` Eric Abrahamsen
2021-04-28 23:29 ` Eric Abrahamsen
2021-05-02 6:52 ` Lars Ingebrigtsen
2021-05-02 16:57 ` Eric Abrahamsen [this message]
2021-05-03 9:01 ` Lars Ingebrigtsen
2021-05-03 16:16 ` Eric Abrahamsen
2021-05-04 8:01 ` Lars Ingebrigtsen
2021-05-04 23:35 ` 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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87im41ul8w.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=47478@debbugs.gnu.org \
--cc=larsi@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).