From: Ken Raeburn <raeburn@raeburn.org>
Cc: ding@gnus.org
Subject: Re: wish list: thread-gathering sort options
Date: Sat, 20 Jul 2002 20:19:02 -0400 [thread overview]
Message-ID: <tx1sn2ec4qx.fsf@raeburn.org> (raw)
In-Reply-To: <m2wurzfdzi.fsf@truxton.com> (Truxton Fulton's message of "Sat, 13 Jul 2002 15:40:49 -0700")
Truxton Fulton <trux@truxton.com> writes:
> I found a work-around that does the trick for me. The thread
> gathering process gathers lower threads up to the higher thread.
> If this could be reversed (since the thread sorting order is also
> reversed), that would solve the problem.
That gets the groups of gathered threads into the proper order, but
wouldn't it put the thread with the latest messages first within each
group? I think I'd want the threads within each gathered group to be
sorted by most-recent number or date too.
Still, it may better than the status quo. Thanks for the suggestion,
I'll try it out. A new thread-gathering function that does something
like:
(reverse (gnus-gather-threads-by-subject (reverse arg)))
(or similarly for -by-references) should accomplish the same.
> I'm sure there's a better way, since this will only do good things
> for those of us with the most recent messages at the bottom of the
> buffer.
True...
Ken
next prev parent reply other threads:[~2002-07-21 0:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-29 18:09 Ken Raeburn
2002-04-29 19:50 ` Kai Großjohann
2002-05-14 8:23 ` Ken Raeburn
2002-05-14 9:32 ` Kai Großjohann
2002-05-14 10:23 ` Ken Raeburn
2002-05-14 10:50 ` Kai Großjohann
2002-05-14 14:16 ` Ken Raeburn
2002-05-14 15:23 ` Kai Großjohann
2002-05-15 16:03 ` Ken Raeburn
2002-05-15 16:53 ` Kai Großjohann
2002-07-13 22:40 ` Truxton Fulton
2002-07-21 0:19 ` Ken Raeburn [this message]
2002-07-21 1:07 ` Ken Raeburn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=tx1sn2ec4qx.fsf@raeburn.org \
--to=raeburn@raeburn.org \
--cc=ding@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).