Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: Gnus refuses to connect after suspend and resume in different network, but Gnus in fresh emacs works
Date: Mon, 30 Jan 2023 12:48:52 -0800	[thread overview]
Message-ID: <87r0vb7npn.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87k0133j6e.fsf@dod.no>

Steinar Bang <sb@dod.no> writes:

>>>>>> Eric Abrahamsen <eric@ericabrahamsen.net>:
>
>> 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.
>
> Hm... I don't have an emacs variable named gnus-dbus-close-on-sleep
>
> gnus-version: Gnus v5.13
> emacs-version: GNU Emacs 27.1 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.24, cairo version 1.16.0) of 2023-01-06, modified by Debian
>
> locate-library says that gnus comes from: ~/git/emacs/lisp/gnus/gnus.elc
>
> The branch of the ~/git/emacs/ repo is called emacs-27-with-gnus-cloud-from-emacs-28
>
> So without checking closer and vaguely remembering setting it up, I'm
> guessing that's what it is: it is the gnus that's in emacs-27 but with
> the gnus-cloud.el file fetched from emacs-28, because the gnus-cloud in
> emacs-27 doesn't work.

Might be time to start running master! There's a lot of good stuff in
upcoming 29.



  reply	other threads:[~2023-01-30 22:22 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 [this message]
2023-08-11 20:31     ` John Haman
2023-08-11 21:26       ` John Haman
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=87r0vb7npn.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).