Re: sort options -- threads/date-received , in reverse order
Hi, * 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? ,[ ~/docs/software/mutt/manual-1.5.1.txt ]- | | 6.3.254 sort_aux | | Type: sort order | | Default: date | | 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. bye, Rocco
Re: sort options -- threads/date-received , in reverse order
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/pgp0.pgp Description: PGP signature
sort options -- threads/date-received , in reverse order
version: 1.4i I want to try a new sort order for my mailling list folders. I am currently using 'sort=threads, sort-aux=date-received'. I've tried adding 'reverse-' to the beginning of each of those, but it isn't the effect I want. What I would like to try is 1) first group the messages according to the thread they are in 2) for each thread, sort the thread itself with date-received 3) order the threads (relative to other threads) in reverse-date-received order Basically I want the same thing I have now, but to reverse the order of the threads, treating each thread as an autonomous unit. The reverse-threads method and the reverse-date-received methods do this, but _also_ invert the contents of each thread. In other words, each thread will be normal (per my current setup), but with the newest thread on top, and so on. Is it possible to achieve what I want with the current code? If not, is this a sensible feature to add to the wishlist? TIA, -D -- There are six things the Lord hates, seven that are detestable to him : haughty eyes, a lying tongue, hands that shed innocent blood, a heart that devises wicked schemes, feet that are quick to rush into evil, a false witness who pours out lies and a man who stirs up dissension among brothers. Proverbs 6:16-19 http://dman.ddts.net/~dman/ msg29619/pgp0.pgp Description: PGP signature
Re: sort options -- threads/date-received , in reverse order
Hi, * Derrick 'dman' Hudson [02-07-14 03:11:37 +0200] wrote: I want to try a new sort order for my mailling list folders. I am currently using 'sort=threads, sort-aux=date-received'. I've tried adding 'reverse-' to the beginning of each of those, but it isn't the effect I want. To answer your question, 'set sort=threads' and 'set sort_aux=reverse-date-received'. What I would like to try is 1) first group the messages according to the thread they are in set sort=threads 2) for each thread, sort the thread itself with date-received 2) doesn't make sence since a thread is already sorted by 1) (according to headers). 3) order the threads (relative to other threads) in reverse-date-received order set sort_aux=reverse-date-received bye, Rocco
Re: sort options -- threads/date-received , in reverse order
On Sun, Jul 14, 2002 at 03:22:32AM +0200, Rocco Rutte wrote: Thanks for your response. | * Derrick 'dman' Hudson [02-07-14 03:11:37 +0200] wrote: | | What I would like to try is | 1) first group the messages according to the thread they are in | | set sort=threads | | 2) for each thread, sort the thread itself with date-received | | 2) doesn't make sence since a thread is already sorted by |1) (according to headers). | | 3) order the threads (relative to other threads) in | reverse-date-received order | | set sort_aux=reverse-date-received That doesn't achieve the effect I want. Here is an example : ~~~ with sort_aux=reverse-date-received 91 r L Jul09 Kurt Lieber (1.2K) Re: return-path user -- local vs. smtp 92 L Jul10 Alexander Saboure(1.3K) |- 93 L Jul10 Philip Hazel (0.4K) | `- 94 L Jul10 Alexander Saboure(0.2K) | |- 95 L Jul10 Alexander Saboure(0.9K) | `- 96 L Jul10 Philip Hazel (0.7K) |- 97 F Jul09 Derrick 'dman' Hu(0.8K) `- ~~~ Notice how, at the same thread level, the older message is at the bottom. (in particular, compare messages 92, 96, and 97. What I want is for that thread to look like this, but still have indices 91-97 (that is, be near the top of the folder) : ~~~ example with sort_aux=date-received 554 r L Jul09 Kurt Lieber (1.2K) Re: return-path user -- local vs. smtp 555 F Jul09 Derrick 'dman' Hu(0.8K) |- 556 L Jul10 Philip Hazel (0.7K) |- 557 L Jul10 Alexander Saboure(1.3K) `- 558 L Jul10 Philip Hazel (0.4K) `- 559 L Jul10 Alexander Saboure(0.9K) |- 560 L Jul10 Alexander Saboure(0.2K) `- ~~~ 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'? -D -- Better a little with righteousness than much gain with injustice. Proverbs 16:8 http://dman.ddts.net/~dman/ msg29623/pgp0.pgp Description: PGP signature
