Re: sort/sort_aux different for sorting threads and sorting within
On Wed, Sep 06, 2006 at 10:10:09PM -0400, Kyle Wheeler wrote:
> On Wednesday, September 6 at 08:15 PM, quoth Patrick Shanahan:
> >>In particular, I'd like to sort my threads
> >>"reverse-last-date-received", but the messages within each thread as
> >>"last-date-received", so that the newest "thread" is on top, but the
> >>oldest message within that thread is the first 'N' message in the
> >>thread.
> >
> >
> >see (in TFM):
FWIW, I've read TFM, as well as tested all 4 combinations.
>
> The key part, in case you missed it, is this:
>
> > 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).
>
> So, if I understand what you're aiming for, this should get you what
> you want:
>
> set sort=reverse-threads
> set sort_aux=reverse-last-date-received
>
that configuration leads to:
377 s! 19:10 Kyle Wheeler (3.6K) /->Re: sort/sort_aux different for
sorting threads and sorting within - --AGZzQgpsuUlWC1xT On Wednesday,
September 6 at 08:15 PM, quoth Patrick Shanahan
378 L 17:15 Patrick Shanaha (3.6K) /-> - * Charles Killian [09-06-06
19:55]: see (in TFM): 3.264. sort_aux Type: sort order Default: date
When sorting by threads, this va [CSID]
379 F 16:37 To mutt-dev@mut (1.2K) sort/sort_aux different for sorting
threads and sorting within threads - When using "threads" sort, is it
possible to use a different sort for sorting thre
380 L 09/03 nate-mutt@refri (4.8K) +->mutt/2465: [PATCH] Use Delivered-to
header in set_reverse_name() - Debian GNU/Linux This patch makes use of the
Delivered-to: header when building the F
381 sL 21:26 Kyle Wheeler (3.6K) | /->Re: mutt/2465: [PATCH] Use
Delivered-to header in - --CEUtFxTsmBsHRLs3 On Thursday, September 7 at
04:45 AM, quoth Derek Martin: On MTAs that do add
382 L 19:45 Derek Martin (2.3K) +->Re: mutt/2465: [PATCH] Use
Delivered-to header in set_reverse_name() - The following reply was made to
PR mutt/2465; it has been noted by GNATS. > This
383 L 21:35 Kyle Wheeler (3.3K) +->Re: mutt/2465: [PATCH] Use
Delivered-to header in - The following reply was made to PR mutt/2465; it
has been noted by GNATS. ?set_reverse_name() --CEU
384 L 21:56 Carthik Sharma (3.1K) Recommendations for mail server account?
- Hi, I regularly use three different computers - a work desktop, a laptop
and a home desktop. I have three email
385 F 22:03 To mutt-users@m (2.7K) /=>
386 F 22:03 To mutt-users@m (1.7K) /-> - This seems like it will work,
I may use it in the meanwhile. The problem with this approach is that to really
get what I want, I'll have t [CSID]
387 rs! 19:01 Kyle Wheeler (3.2K) /-> - On Wednesday, September 6 at
04:28 PM, quoth Charles Killian: You can achieve this with a message-hook and a
pager macro. Like so: mes [CSID]
388 F 16:28 To mutt-users@m (1.3K) Modifying a message from the pager,
return to mailbox - I recently wanted to set mutt up so that when I delete a
message, it does not read the next message
You'll see that this puts the thread with the newest last-date-received message
farthest down in the mailbox, I actually want the threads in the other order.
The order I actually want is:
388 F 16:28 To mutt-users@m (1.3K) Modifying a message from the pager,
return to mailbox - I recently wanted to set mutt up so that when I delete a
message, it does not read the next message
387 rs! 19:01 Kyle Wheeler (3.2K) \-> - On Wednesday, September 6 at
04:28 PM, quoth Charles Killian: You can achieve this with a message-hook and a
pager macro. Like so: mes [CSID]
386 F 22:03 To mutt-users@m (1.7K) \-> - This seems like it will work,
I may use it in the meanwhile. The problem with this approach is that to really
get what I want, I'll have t [CSID]
385 F 22:03 To mutt-users@m (2.7K) \=>
384 L 21:56 Carthik Sharma (3.1K) Recommendations for mail server account?
- Hi, I regularly use three different computers - a work desktop, a laptop
and a home desktop. I have three email
380 L 09/03 nate-mutt@refri (4.8K) +->mutt/2465: [PATCH] Use Delivered-to
header in set_reverse_name() - Debian GNU/Linux This patch makes use of the
Delivered-to: header when building the F
382 L 19:45 Derek Martin (2.3K) +->Re: mutt/2465: [PATCH] Use
Delivered-to header in set_reverse_name() - The following reply was made to
PR mutt/2465; it has been noted by GNATS. > This
381 sL 21:26 Kyle Wheeler (3.6K) | \->Re: mutt/2465: [PATCH] Use
Delivered-to header in - --CEUtFxTsmBsHRLs3 On Thursday, September 7 at
04:45 AM, quoth Derek Martin: On MTAs that do add
383 L 21:35 Kyle Wheeler (3.3K) +->Re: mutt/2465: [PATCH] Use
Delivered-to header in - The following reply was made to PR mutt/2465; it
has been noted by GNATS. ?set_reverse_name() --CEU
379 F 16:37 To mutt-dev@mut (1.2K) sort/sort_aux different for sorting
threads and sorting within threads - When using "threads" sort, is it
possible to use a different sort for sorting thre
378 L 17:15 Patrick Shanaha (3.6K) \-> - * Charles Killian [09-06-06
19:55]: see (in TFM): 3.264. sort_aux Type: sort order Default: date
When sorting by threads, this va [CSID]
377 s! 19:10 Kyle Wheeler (3.6K) \->Re: sort/sort_aux different for
sorting threads and sorting within - --AGZzQgpsuUlWC1xT On Wednesday,
September 6 at 08:15 PM, quoth Patrick Shanahan
(I've left the message numbers from the original for easy mapping.) In this
order, the thread with the latest earliest-date-first is first. Within that
thread, newer messages are below older ones. Also, within each thread,
messages at the same layer are sorted such that subthread with
latest-message-received is last. (i.e., within one thread, the order should
match the order by:
set sort=threads
set sort_aux=last-date-received
).
But the threads themselves appear in the reverse order from that sorting. This
keeps the top-down flow within a thread which I like, but brings newer threads
to the top of the mailbox.
Thanks
--Chip
--
====
Chip Killian
http://chip.kcubes.com