From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: ProtonMail Bridge Patch
Date: Thu, 22 Feb 2024 18:23:29 -0800 [thread overview]
Message-ID: <871q93hqam.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87a5nsruc2.fsf@kubajecminek.cz>
Jakub Ječmínek <kuba@kubajecminek.cz> writes:
> "Eric Abrahamsen" <eric@ericabrahamsen.net> writes:
>
>> Yes! That's it, thanks very much. The question remains where exactly to
>> address this, but it's good to know why it's behaving this way. I'll put
>> this on the list.
>
> I don't think we have good/elegant way to do it. I see two options:
>
> 1. Implement custom sorting in nnimap.el back end.
>
> This would require substantial work because we'd have to modify all the
> definitions where we perform FETCH & SEARCH (AFAIK these two commands
> are the only affected).
It's possible that all that would be necessary is to add a routine at
the bottom of `nnimap-transform-headers', to sort the buffer text. The
SEARCH command is handled differently, I believe.
> 2. Modify the functions in gnus-range.el to accept unsorted lists
>
> I don't know the internals good enough to tell if this would be
> enough. There might be other parts in Gnus which also expect sorted
> headers/messages/lists/etc that I'm not aware of.
I don't think modifying gnus-range is a good idea -- if that code
requires sorted ranges, we should just make sure it's always given
sorted ranges.
next prev parent reply other threads:[~2024-02-23 2:23 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
2024-02-22 17:18 ` Eric Abrahamsen
2024-02-22 22:46 ` Jakub Ječmínek
2024-02-23 2:23 ` Eric Abrahamsen [this message]
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=871q93hqam.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).