summaryrefslogtreecommitdiff
path: root/commands/choose.go
diff options
context:
space:
mode:
authorcos <cos>2022-07-26 13:03:57 +0200
committercos <cos>2022-07-26 13:03:57 +0200
commita70697d1224cbb13dae99a50238e62650eee587c (patch)
treeb04b738091cc2678f11476ff6a26b95f63cc1cc3 /commands/choose.go
parent12dec19109f4ad91f60a2f012f1556bcf78312e9 (diff)
downloadaerc-wip/asc_sort_imap.zip
Hack up message list to be sorted ascendingwip/asc_sort_imap
By default aerc is designed to revert sorting of the message list in descending order. It's some kind of yolo thing? Possibly an attempt to cater to Outlook and Gmail users who never ever act on messages, but merely read the latest arrivals and leave them in the INBOX. There is a sort command as well as a sort config option, but they silently do not work with imap. According to #aerc on Libera.chat it should work with other email storage methods, but I haven't tried. When aerc is fetching the list of messages, it is done by first sending a 'UID THREAD REFERENCES "UTF-8" (ALL)' to the server, and then proceeding to actually fetch messages in sane order. The reverse happens later (in files modified by this commit). Supposedly reversing of order with other backends are done once while building the data structure, and is then reversed again when traversing it. One could have the idea of doing the same with imap, but that is an impossible (or at least impractical) thought to consider, since the imap grammar does not support combining threaded search and reversed sorting if I understand [rfc5256s5][] correctly. This patch merely fixes up aerc to be useful to me. Please approach me on Libera.chat for discussing a proper fix. I'm known as |cos| there. [rfc5256s5]: https://datatracker.ietf.org/doc/html/rfc5256#section-5
Diffstat (limited to 'commands/choose.go')
0 files changed, 0 insertions, 0 deletions