From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: Gnus sometimes reports new messages but not showing them on IMAP server
Date: Sun, 21 Apr 2024 19:35:53 -0700 [thread overview]
Message-ID: <87wmoqjf92.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <rmio7a2mfkj.fsf@s1.lexort.com>
Greg Troxel <gdt@lexort.com> writes:
> Arash Esbati <arash@gnu.org> writes:
>
>>> I've focused on figuring out why the active number goes wrong, but in
>>> the interest of pragmatism it might be better just to make sure that
>>> nnimap always does the equivalent of "M-g" at Gnus startup.
>>
>> That might be a good compromise.
>
> Agreed. It seems obvious (said knowing that's dangerous) that on
> starting up the program, it's best not to rely on state that could be
> wrong. That's tricky, because mail programs keep messages and don't
> refetch them, but relying on counts of unread seems very trouble prone,
> vs "I have this message body and the timestamp matches so I won't fetch
> it."
>
> I think it would also be good to separate
>
> check for new
>
> get all the messages that are there
>
> really rescan and don't believe state
>
> in terms of being much louder about the differences. I have the
> impression that the assembled gnususers here are at least somewhat hazy
> on those boundaries. At least I am.
I think this is an artifact of Gnus starting out as a newsreader, and
adding email capability later. In a NNTP context, the read/unread
message count is entirely private to your local machine, and something
you can manipulate at will. In an IMAP context, it's very much a part of
multi-machine state. Gnus should always defer to the remote server,
particularly at start up. I do wish I knew where the bug was coming
from, though.
next prev parent reply other threads:[~2024-04-22 2:36 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-12 0:57 Xiyue Deng
2024-04-17 0:03 ` Greg Troxel
2024-04-17 6:47 ` Xiyue Deng
2024-04-17 19:51 ` Dan Christensen
2024-04-18 12:13 ` Greg Troxel
2024-04-19 22:55 ` Dan Christensen
2024-04-21 12:08 ` Arash Esbati
2024-04-21 12:43 ` Dan Christensen
2024-04-21 13:14 ` Andreas Schwab
2024-04-21 16:18 ` Eric Abrahamsen
2024-04-21 18:16 ` Arash Esbati
2024-04-22 0:00 ` Greg Troxel
2024-04-22 2:35 ` Eric Abrahamsen [this message]
2024-04-27 19:46 ` Xiyue Deng
2024-05-02 5:47 ` Xiyue Deng
2024-05-02 15:08 ` Eric Abrahamsen
2024-05-02 17:24 ` Xiyue Deng
2024-05-02 17:41 ` Dan Christensen
2024-05-02 18:41 ` Xiyue Deng
2024-05-05 20:18 ` Xiyue Deng
2024-05-05 21:01 ` Dan Christensen
2024-05-05 22:10 ` Xiyue Deng
2024-04-24 15:23 ` James Thomas
2024-04-25 2:59 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wmoqjf92.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).