tom.hirschowitz at univ-smb.fr
Fri Mar 6 02:41:58 PST 2020
The order returned by notmuch with the oldest-first option looks wrong
to me: as far as I can see, threads are sorted according to their oldest
unread message, but in any case, it is not the converse of the
Is this a bug? And if not, how hard would it be to add an option for
getting the converse of newest-first?
Thanks in advance for any help!
More information about the notmuch