On Sun, Jul 22, 2012 at 7:32 AM, Patrick Shanahan <[email protected]> wrote: > I believe you are out-of-luck. >> My current .muttrc states: >> set sort=threads >> set sort_aux=reverse-last-date-received > > But, iiuc the docs state that "sort_aux" applies to the order "threads" > are sorted and *not* the order of msgs within a thread.
Greetings Patrick , Here's an extract from my .muttrc, I also should have stated that I'm using Mutt 1.5.21 , on Ubuntu 12.04 . However this behavior is the same on different distributions that I use. Begin=== #When sorting by threads, this variable controls how threads are sorted # in relation to other threads, and how the branches of the thread trees # are sorted. This can be set to any value that ``$sort'' can, except # threads (in that case, mutt will just use date-sent). You can also # specify the last- prefix in addition to the reverse- prefix, but last- # must come after reverse-. The last- prefix causes messages to be # sorted against its siblings by which has the last descendant, using # the rest of sort_aux as an ordering. For instance, set sort_aux=last- # date-received would mean that if a new message is received in a # thread, that thread becomes the last one displayed (or the first, if # you have set sort=reverse-threads.) Note: For reversed ``$sort'' # order $sort_aux is reversed again (which is not the right thing to do, # but kept to not break any existing configuration setting). End=== >From the above, I conclude that set_sort_aux may have a say about how messages are arranged withing a thread. If, I could not get messages to appear in good order , within a thread, at all, then, my thoughts may have been different. All seems to be working fine, as long as I keep my newest emails on the bottom of the list (and that's sort of counter-intuitive for me ) . Thank you . -- Guy Gold -- Guy Gold
