From: Steinar Bang <sb@dod.no>
To: ding@gnus.org
Subject: Re: Trying to use gnus-cloud: what's the pinentry dialog? (and how can I get rid of it?)
Date: Mon, 04 Oct 2021 16:43:30 +0200 [thread overview]
Message-ID: <86wnmsj1f1.fsf@dod.no> (raw)
In-Reply-To: <867deuj9sl.fsf@dod.no>
>>>>> Steinar Bang <sb@dod.no>:
> With the parsing errors fixed... or at least: worked around, ~-RET still
> doesn't update the group read count.
> In the minibuffer and in the Messages buffer, I see messages like this:
> Skipping outdated cloud info for group nntp+news.gmane.io:gmane.mail.davmail.user, the info is from 2021-10-03T19:11:07+0200 (now is 2021-10-03T19:14:11+0200)
> Is this a bug in gnus-cloud?
I don't see how this could work...?
https://git.savannah.gnu.org/cgit/emacs.git/tree/lisp/gnus/gnus-cloud.el?h=emacs-27#n232
https://git.savannah.gnu.org/cgit/emacs.git/tree/lisp/gnus/gnus-cloud.el?h=emacs-27#n241
Ie. unless you play tricks with the system clocks on the computers
involved in the sync, there is no way the written time stamp isn't older
than the current time (and the sync will fail to update).
And indeed the master version of the same function looks quite
different:
https://git.savannah.gnu.org/cgit/emacs.git/tree/lisp/gnus/gnus-cloud.el?h=master#n222
(the emacs-28 version of the function looks the same as master)
Here's the change to the method:
https://git.savannah.gnu.org/cgit/emacs.git/commit/lisp/gnus/gnus-cloud.el?id=a77ac015b3fecc4a63ae42712b693e3158fc5452&h=master
commit a77ac015b3fecc4a63ae42712b693e3158fc5452
Author: David Edmondson <dme@dme.org>
Date: Sat Mar 28 19:03:58 2020 +0000
gnus-cloud: Improve cloud sync
After replaying a set of actions downloaded by gnus-cloud, persist the
highest sequence number seen as the local `gnus-cloud-sequence'
number, in order that a future download will not unnecessarily replay
previously seen actions and any future uploads from this emacs
instance use a higher sequence number than that downloaded.
Remove the test on whether individual newsrc entries are older than
the current time, as that is always going to be the case.
I wonder if emacs-28 gnus will run on emacs-27? What about emacs-26?
I will try, and report back.
next prev parent reply other threads:[~2021-10-04 14:44 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-19 13:50 Steinar Bang
2021-09-19 14:16 ` Steinar Bang
2021-09-19 14:30 ` Steinar Bang
2021-09-19 14:47 ` Steinar Bang
2021-09-23 15:07 ` Steinar Bang
2021-09-23 15:25 ` Steinar Bang
2021-09-23 17:17 ` Steinar Bang
2021-09-23 17:42 ` Steinar Bang
2021-09-23 17:58 ` dick
2021-09-24 8:40 ` Eric S Fraga
2021-09-24 20:18 ` Steinar Bang
2021-09-26 15:44 ` Eric S Fraga
2021-09-26 16:52 ` Steinar Bang
2021-09-27 14:54 ` Eric S Fraga
2021-10-02 11:27 ` Steinar Bang
2021-10-02 11:39 ` Steinar Bang
2021-10-02 14:59 ` Steinar Bang
2021-10-02 15:49 ` Eric Abrahamsen
2021-10-02 16:19 ` Steinar Bang
2021-10-03 8:46 ` Steinar Bang
2021-10-03 17:30 ` Steinar Bang
2021-10-04 14:43 ` Steinar Bang [this message]
2021-10-04 18:00 ` Steinar Bang
2021-10-04 19:19 ` Steinar Bang
2021-10-04 19:42 ` Steinar Bang
2021-10-04 20:09 ` Adam Sjøgren
2021-10-04 21:26 ` Steinar Bang
2021-10-05 8:41 ` Robert Pluim
2021-10-05 15:02 ` Adam Sjøgren
2021-10-05 15:41 ` Robert Pluim
2021-10-05 16:20 ` Adam Sjøgren
2021-10-05 15:14 ` Eric Abrahamsen
2021-10-05 16:17 ` Adam Sjøgren
2021-10-05 17:46 ` Eric Abrahamsen
2021-10-05 17:52 ` Adam Sjøgren
2021-09-23 17:14 ` 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=86wnmsj1f1.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).