Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Emanuel Berg <embe8573@student.uu.se>
To: info-gnus-english@gnu.org
Subject: Re: Sorting threads after gathering threads
Date: Wed, 30 Jul 2014 02:48:14 +0200	[thread overview]
Message-ID: <878unbisdt.fsf@debian.uxu> (raw)
In-Reply-To: <mailman.6260.1406678726.1147.info-gnus-english@gnu.org>

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.

Check out `gnus-summary-thread-gathering-function'.
I have that gnus-gather-threads-by-subject.

    ... Function used for gathering loose threads.
    There are two pre-defined functions:
    `gnus-gather-threads-by-subject', which only takes
    Subjects into consideration; and
    `gnus-gather-threads-by-references', which compared
    the References headers of the articles to find
    matches.

-- 
underground experts united

  parent reply	other threads:[~2014-07-30  0:48 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
     [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 [this message]
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=878unbisdt.fsf@debian.uxu \
    --to=embe8573@student.uu.se \
    --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).