Gnus development mailing list
 help / color / mirror / Atom feed
From: "Jakub Ječmínek" <kuba@kubajecminek.cz>
To: ding@gnus.org
Subject: Re: ProtonMail Bridge Patch
Date: Tue, 20 Feb 2024 11:59:08 +0000	[thread overview]
Message-ID: <87cysruz1x.fsf@kubajecminek.cz> (raw)
In-Reply-To: <87y1bhmxqa.fsf@ericabrahamsen.net>

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

> Huh. Yeah, I absolutely believe it's true, I just wish I could pinpoint
> where.

Ok, I think I've found it. The problem is that we're feeding unsorted
lists into a bunch of functions that require lists to be sorted (a lot
of functions do in 'gnus-range.el').

**Example 1:**
Inside the body of 'gnus-select-newsgroup' ('gnus-sum.el').

(setq gnus-newsgroup-unreads
	    (gnus-sorted-nintersection
	     gnus-newsgroup-unreads fetched-articles))

...

(gnus-update-missing-marks
  (gnus-sorted-difference articles fetched-articles))


**Example 2:**
Inside the body of 'nnimap-update-info' ('nnimap.el').

(let* ((unread (gnus-compress-sequence
		(gnus-set-difference
		 (gnus-set-difference
		  existing
		  (gnus-sorted-union
		   (cdr (assoc '%Seen flags))
		   (cdr (assoc '%Deleted flags))))
		 (cdr (assoc '%Flagged flags)))))
       (read (range-difference
	      (cons start-article high) unread)))

-- 
Kuba Ječmínek (http://kubajecminek.cz)



  reply	other threads:[~2024-02-20 11:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-17 17:29 Jakub Ječmínek
2024-02-17 18:05 ` Eric Abrahamsen
2024-02-17 18:44   ` Jakub Ječmínek
2024-02-18 17:43     ` Eric Abrahamsen
2024-02-18 17:57       ` Jakub Ječmínek
2024-02-18 18:30         ` Eric Abrahamsen
2024-02-20 11:59           ` Jakub Ječmínek [this message]
2024-02-22 17:18             ` Eric Abrahamsen
2024-02-22 22:46               ` Jakub Ječmínek
2024-02-23  2:23                 ` Eric Abrahamsen
2024-02-23 11:57                   ` Jakub Ječmínek
2024-02-19 18:23         ` Bjørn Mork
2024-02-19 21:40           ` 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=87cysruz1x.fsf@kubajecminek.cz \
    --to=kuba@kubajecminek.cz \
    --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).