Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Michael Welsh Duggan <mwd@md5i.com>
To: info-gnus-english@gnu.org
Subject: Re: Sorting threads after gathering threads
Date: Tue, 29 Jul 2014 22:52:42 -0400	[thread overview]
Message-ID: <87lhrbh81x.fsf@maru2.md5i.com> (raw)
In-Reply-To: <87d2cnisrn.fsf@debian.uxu>

Emanuel Berg <embe8573@student.uu.se> writes:

> Michael Welsh Duggan <mwd@md5i.com> writes:
>
>> The important part here is that these are not real
>> threads. They are individual messages with enough
>> similarities that threading can be simulated. In Gnus
>> parlance, they are "loose threads," and are put
>> together during "thread gathering." Unfortunately, it
>> seems like thread gathering happens after thread
>> sorting, for some unknown reason.
>
> What does the distinction loose or real thread matter?
> Why can't you have them all grouped by subject and then
> sorted by number (or date) within each group?

You seem to be missing my point.  There are no threads to start -- or
rather, every message is its own thread.  Then they get sorted by the
`gnus-thread-sort-functions'.  Then the remaining threads (all
individual messages still) are gathered as loose threads into real
threads.  Then the messages are sorted within each gathered thread.  But
the threads are no longer properly sorted with respect to each other,
since the sorting was done before the gathering.  See
`gnus-summary-prepare':

    ;; Generate the buffer, either with threads or without.
    (when gnus-newsgroup-headers
      (gnus-summary-prepare-threads
       (if gnus-show-threads
	   (gnus-sort-gathered-threads
	    (funcall gnus-summary-thread-gathering-function
		     (gnus-sort-threads
		      (gnus-cut-threads (gnus-make-threads)))))
	 ;; Unthreaded display.
	 (gnus-sort-articles gnus-newsgroup-headers))))

I am wondering why the sorting (of threads) happens before the gathering
into threads.

-- 
Michael Welsh Duggan
(md5i@md5i.com)



  reply	other threads:[~2014-07-30  2:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.6108.1406500221.1147.info-gnus-english@gnu.org>
2014-07-27 22:55 ` Emanuel Berg
2014-07-30  0:04   ` Michael Welsh Duggan
     [not found]   ` <mailman.6260.1406678726.1147.info-gnus-english@gnu.org>
2014-07-30  0:39     ` Emanuel Berg
2014-07-30  2:52       ` Michael Welsh Duggan [this message]
     [not found]       ` <mailman.6268.1406688789.1147.info-gnus-english@gnu.org>
2014-07-30  3:04         ` Emanuel Berg
2014-07-30  0:48     ` Emanuel Berg
2014-07-27 22:27 Michael Welsh Duggan
2014-08-12  0:15 ` Dan Christensen
2014-08-12 11:20 ` N. Raghavendra

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=87lhrbh81x.fsf@maru2.md5i.com \
    --to=mwd@md5i.com \
    --cc=info-gnus-english@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 NNTP newsgroup(s).