Gnus development mailing list
 help / color / mirror / Atom feed
From: Steinar Bang <sb@dod.no>
To: ding@gnus.org
Subject: Re: Emacs 28.2 gnus: nntp read marks lost after going offline and online again
Date: Wed, 21 Jun 2023 20:46:39 +0200	[thread overview]
Message-ID: <87y1kc8xgw.fsf@dod.no> (raw)
In-Reply-To: <87fs6ltwz7.fsf@ericabrahamsen.net>

>>>>> Eric Abrahamsen <eric@ericabrahamsen.net>:

> Yes, in your previous image of the Server buffer note all the
> (cloud-sync) tags after servers, and the one (CLOUD-HOST). I've only
> tried the gnus-cloud thing once several years ago, but the manual makes
> it sound like you'd have to enable it manually -- did you not do that?

Well, I have enabled it on a much older version of gnus, on September 23
2021, and it may be that my old enablement doesn't work too well with
the current version.

Hm... digging further into the git history, I have tried using
gnus-cloud since July 24 2016, but I didn't have any success until
around 2019, and I didn't retire its predecessor gnus-sync until 2021
(when it stopped working).

There are some posts and threads. on this list about my experiments.
Probably last time was around the previous debian major version upgrade
when emacs switched from 26 to 27.

Also I have been running a hacked version of gnus-cloud, since the one
bundled with earlier gnus versions didn't work right.

Now I'm running with the plain emacs 28 gnus.

These are my settings to enable gnus-cloud:
(setq gnus-cloud-interactive nil
      gnus-cloud-method "nnimap:cloud"
      gnus-cloud-storage-method nil
      gnus-cloud-synced-files '((:directory "~/News" :match ".*.SCORE\\'"))
      mail-source-movemail-program "movemail")

(the movemail setting is gnus cloud related from August 18 2019, when
switching from emacs 25 to emacs 26 after a debian upgrade)

> Anyway, even if gnus-cloud isn't the culprit it's likely to make
> debugging harder. Try using "i" to toggle the cloud-sync servers, and
> "I" to toggle the CLOUD-HOST server -- hopefully that will shut it off
> altogether...

Ok. I'll try that and if that doesn't work I'll remove the gnus-cloud
config.

Am I the only current user of gnus-cloud, I wonder?



  reply	other threads:[~2023-06-21 18:47 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-19 14:52 Steinar Bang
2023-06-19 16:27 ` Steinar Bang
2023-06-19 17:44   ` Steinar Bang
2023-06-19 18:16     ` dick
2023-06-20 17:00       ` Steinar Bang
2023-06-20 18:03         ` dick
2023-06-19 20:09     ` Steinar Bang
2023-06-20 19:24     ` Steinar Bang
2023-06-20 19:52       ` Steinar Bang
2023-06-21  1:39         ` Eric Abrahamsen
2023-06-21 18:46           ` Steinar Bang [this message]
2023-06-21 19:54             ` Steinar Bang
2023-06-21 20:05               ` Steinar Bang
2023-06-21 20:45                 ` Steinar Bang
2023-06-21 20:55                   ` Steinar Bang
2023-06-21 22:49                     ` Eric Abrahamsen
2023-06-22 16:55                       ` Steinar Bang
2023-06-25 14:21                         ` Steinar Bang
2023-06-22 13:52                     ` Dan Christensen
2023-06-24  5:52                       ` Steinar Bang
2023-06-25 13:34                         ` Dan Christensen
2023-06-25 14:35                           ` Steinar Bang
2023-06-26  0:58                             ` list level not respected by gnus-group-get-new-news [was: Emacs 28.2 gnus: nntp read marks lost after going offline and online again] Dan Christensen
2023-06-27 17:13                               ` Steinar Bang
2023-06-19 16:37 ` Emacs 28.2 gnus: nntp read marks lost after going offline and online again dick

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=87y1kc8xgw.fsf@dod.no \
    --to=sb@dod.no \
    --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).