unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Tassilo Horn <tsdh@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Sorting with threads in Gnus
Date: Fri, 26 Jul 2013 15:06:15 +0200	[thread overview]
Message-ID: <87ppu5wjw8.fsf@thinkpad.tsdh.org> (raw)
In-Reply-To: 87d2q5lmo3.fsf@ericabrahamsen.net

Eric Abrahamsen <eric@ericabrahamsen.net> writes:

>> I hoped that `gnus-thread-sort-functions' was applied only to thread
>> roots, and `gnus-sort-gathered-threads-function' to subthreads, but
>> that doesn't seem to be tha case.
>
> Huh, interesting -- I hadn't realized subthreads were sorted as well,
> but they are: gnus-sort-threads calls the appropriately-named
> gnus-sort-threads-recursive.

Funnily, I also didn't notice that for years.  But now that I do, it
started annoying me.

> That's hard-coded, and there's nothing to distinguish a top-level
> thread from a subthread.

Well, I'd say a thread root doesn't really need to be the real root of a
thread, just the top-level article that's displayed by Gnus in the
summary buffer (which depends on `gnus-fetch-old-headers' and others).
And I guess that's identitfiable, e.g., the articles that get their
summary thread tree style from `gnus-sum-thread-tree-root',
`gnus-sum-thread-tree-false-root', and
`gnus-sum-thread-tree-single-indent' are the root articles of a thread.

> But I'll bet with a little care, it would be possible to make a
> gnus-sort-threads-recursively-p option, which would have
> gnus-sort-threads break to gnus-sort-articles after the first round of
> sorting... Maybe.

That would be awesome.

Bye,
Tassilo




  reply	other threads:[~2013-07-26 13:06 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-23  8:49 Sorting with threads in Gnus N. Raghavendra
2013-07-24  6:21 ` Eric Abrahamsen
2013-07-24  8:17   ` N. Raghavendra
2013-07-24 13:15   ` Tassilo Horn
2013-07-26  4:37     ` Eric Abrahamsen
2013-07-26  5:48       ` Tassilo Horn
2013-07-26  9:01         ` Eric Abrahamsen
2013-07-26 13:06           ` Tassilo Horn [this message]
2013-07-26 13:26             ` Tassilo Horn
2013-07-26 13:43               ` Tassilo Horn
2013-07-26 15:26                 ` Eric Abrahamsen
2013-07-26 16:56                   ` Tassilo Horn
2013-07-27  7:08                     ` Eric Abrahamsen
2013-07-26 17:40                 ` N. Raghavendra
2013-07-27  8:56                   ` Tassilo Horn
2013-07-27  9:19                     ` N. Raghavendra
2013-07-29  6:53                       ` Tassilo Horn
2013-07-29  7:42                         ` N. Raghavendra
2013-07-28  7:09                     ` N. Raghavendra
2013-07-28  8:03                       ` Michael Heerdegen
2013-07-28  9:50                         ` N. Raghavendra
2013-07-28 12:45                           ` Michael Heerdegen
2013-07-28 16:17                             ` N. Raghavendra
2013-07-30  7:05                               ` Tassilo Horn
2013-07-30  7:24                                 ` Eric Abrahamsen
2013-07-30  8:01                                   ` Tassilo Horn
2013-07-30 10:53                                     ` Eric Abrahamsen
2013-07-29  5:16                             ` N. Raghavendra
2013-07-30  8:07                       ` Tassilo Horn
2013-07-30 11:00                         ` N. Raghavendra
2013-07-30 12:33                           ` Tassilo Horn

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ppu5wjw8.fsf@thinkpad.tsdh.org \
    --to=tsdh@gnu.org \
    --cc=help-gnu-emacs@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).