No, how do I enable those?
I looked at the default config files[1] and couldn't find those keys.

~tmpod

[1]: https://git.sr.ht/~rjarry/aerc/tree/master/item/config

Thank you a lot for your detailed response!

> 1. We search IMAP for all messages in the folder. IMAP responds with a list in
>    ascending date order. We reverse the list so that the list is in descending
>    order. Let's say the UIDs for this list are 1:5000, with 5000 being the
>    newest message. If the server supports SORT, we get the list in the order we
>    want and we don't have to reverse it in the '-r' case
> 2. We download the headers for the visible messages, let's say this is
>    4950:5000. IMAP will respond with the headers in 4950:5000 order. Because of
>    we receive 4950 before 5000. Even for IMAP servers that support SORT, they
>    will return headers like this (FETCH commands are unaffected by SORT)

I see now, IMAP doesn't support sorting in those header windows, quite
unfortunate :(

No, I'd like to get the "-r date" sorting, but fetch/receive the newest
messages first. At the moment, the list is properly sorted, but messages
start coming in from oldest to newest (in that page).

I just tried commenting that config and it surprisingly made no
difference. The message list filled from bottom to top, with the newest
mail at the top.
So does the protocol not support specifying a sort and we just get what
each implementation decides to go with?

Hello!

First of all, a big thank you to all contributors and maintainers, aerc
is my daily driver email client :D

Now, I prefer sorting my email list simply by newest first (sort="-r
date"). However, aerc seems to always fetch the page from oldest to
newest, which turns out to be a bit inconvenient when using slow
Internet, since it can take a hot minute to load the top messages which
are of most interest to me. 
(I know I should organize my inbox email better to avoid having full
pages hehe 😅)

Is it possible to load mail in this order (perhaps a configurable or

The title is pretty self-explanatory.

At first, I thought this was caused by the extra space in the bind
definition, since the popup was triggered if I did <C-l> then deleted
one of the spaces. However, I fixed that and it still didn't trigger the
popup.
I could contribute a patch, but I'm unsure what the issue here is.

Thanks
~tmpod

Really solid update for aerc!
Even though it's not directly included in the changelog, I noticed a 
significant improve in message fetching. Maybe it has to do with the 
race conditions?
Either way, awesome work from everyone involved, congrats!

Thank you.
~tmpod

Congrats on a new wonderful release!

> There's a way to that correctly, right? Or should I just send the entire 
> diff so that it shows up in each new version of the patch, for context's 
> sake?

Yeah, you should just send the diff in its entirety, afaik. `git send-email`
will put the commit message at the top, then the diff, with the option to put
on a cover letter between the commit message and the diff. I believe that is
the only place you should edit things.

Also, it seems like something broke with the mailing list's patch
recognition; it doesn't show diff hightlighting nor the usual patch controls.
Did you send the patch by standard means?