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: Sun, 03 Oct 2021 19:30:18 +0200 [thread overview]
Message-ID: <867deuj9sl.fsf@dod.no> (raw)
In-Reply-To: <86k0iujy28.fsf@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?
Or is this my usage pattern?
I have tried waiting long from saving until reading sync data in case
the problem was that the computers were out of sync (I didn't think so,
since they are both updating from the same NTP server).
And it's impossible not to update the sync client gnus before reading
sync data, because otherwise it doesn't see the new sync message in the
map folder.
Is there a particular order a local update should be done in with
respect to the saved timestamp in the sync info?
next prev parent reply other threads:[~2021-10-03 17:30 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 [this message]
2021-10-04 14:43 ` Steinar Bang
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=867deuj9sl.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).