From: Michael Welsh Duggan <mwd@md5i.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 56332@debbugs.gnu.org
Subject: bug#56332: 29.0.50; Large gnus imap groups; articles incorrectly marked as read (old)
Date: Fri, 01 Jul 2022 11:56:58 -0400 [thread overview]
Message-ID: <87bku87rn9.fsf@md5i.com> (raw)
In-Reply-To: <87o7y9xjhd.fsf@gnus.org> (Lars Ingebrigtsen's message of "Fri, 01 Jul 2022 11:36:30 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Michael Welsh Duggan <md5i@md5i.com> writes:
>
>> I have a large, sparse imap folder with read and unread articles. In
>> recent versions of Emacs, when I visit this group, a set of articles in
>> the middle (when sorted by number) are marked as read with the
>> `O' mark.
>
> And they should be unread?
>
>> I've attached the FETCH command used by last "good" version and the ones
>> issued by a build with the offending commit. In the "bad" version, the
>> articles from 60795 until 63651 are marked as read with an `O'.
>
> Hm. Those are pretty much in the middle... If nnimap fails to parse
> the headers, I'd expect everything after the failure to be missing in
> the Summary buffer, not be marked as read.
>
> Do you use the Gnus cache or the Gnus Agent?
I do not.
--
Michael Welsh Duggan
(md5i@md5i.com)
prev parent reply other threads:[~2022-07-01 15:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-01 6:47 bug#56332: 29.0.50; Large gnus imap groups; articles incorrectly marked as read (old) Michael Welsh Duggan
2022-07-01 9:36 ` Lars Ingebrigtsen
2022-07-01 9:50 ` Lars Ingebrigtsen
2022-07-01 15:54 ` Michael Welsh Duggan
2022-07-01 15:56 ` Michael Welsh Duggan
2022-07-02 12:00 ` Lars Ingebrigtsen
2022-07-02 14:30 ` Michael Welsh Duggan
2022-07-02 15:23 ` Lars Ingebrigtsen
2022-07-02 16:00 ` Michael Welsh Duggan
2022-07-02 16:40 ` Michael Welsh Duggan
2022-07-03 10:59 ` Lars Ingebrigtsen
2022-07-03 14:50 ` Michael Welsh Duggan
2022-07-04 10:49 ` Lars Ingebrigtsen
2022-07-01 15:56 ` Michael Welsh Duggan [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bku87rn9.fsf@md5i.com \
--to=mwd@md5i.com \
--cc=56332@debbugs.gnu.org \
--cc=larsi@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).