On Sun, Jul 14, 2002 at 02:15:10PM +0200, Rocco Rutte wrote: | * Derrick 'dman' Hudson [02-07-14 05:32:13 +0200] wrote: | > On Sun, Jul 14, 2002 at 03:22:32AM +0200, Rocco Rutte wrote:
| > | set sort=threads
| > | set sort_aux=reverse-date-received
|
| > That doesn't achieve the effect I want. Here is an example :
|
| [...]
|
| > Notice how the thread itself is in 'date-received' order.
|
| > However, I want the threads (eg if I collapse-all and then only count
| > the visible messages) to be reverse-date-received.
|
| > Does this make sense now? Do you see how what I want is different
| > from 'sort=threads sort_aux=reverse-date-received'?
|
| I think I got it. You want all threads to be reverse-date
| sorted. And per thread and threading-level you want the
| messages sorted by date received. Is that correct now?
Yes, that is correct.
| ,----[ ~/docs/software/mutt/manual-1.5.1.txt ]-
| |
| | 6.3.254 sort_aux
| | 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.
| `-
|
| So, you'll have to sort by threads and find something to use
| for $sort_aux which fits your needs. You want a thread
| internally sorted by 'date-received' and externally by
| 'reverse-date-received'. That doesn't seem to be possible
| since $sort_aux is used for both.
Yeah, I was afraid it wasn't possible right now. What is the formal
method for submitting a feature request, along with some ideas on how
the feature could be handled? (eg a $sort_aux_threads variable for
intra-thread sorting, which only has effect if
sort=(reverse-)?threads)
-D
--
He who finds a wife finds what is good
and receives favor from the Lord.
Proverbs 18:22
http://dman.ddts.net/~dman/
msg29637/pgp00000.pgp
Description: PGP signature
