From: Emanuel Berg <embe8573@student.uu.se>
To: info-gnus-english@gnu.org
Subject: Re: Sorting threads after gathering threads
Date: Mon, 28 Jul 2014 00:55:57 +0200 [thread overview]
Message-ID: <87ha225s3m.fsf@debian.uxu> (raw)
In-Reply-To: <mailman.6108.1406500221.1147.info-gnus-english@gnu.org>
Michael Welsh Duggan <mwd@md5i.com> writes:
> I am on an automated mailing list which I
> automatically filter into a separate Gnus group. Each
> message on this list is an individual, non-threaded
> messages. Many of these messages are indeed related,
> and this can be determined by the subject. I have put
> my own subject-simplifying function in the
> gnus-simplify-subject-functions' variable for this
> group. This correctly gathers the individual messages
> into threads ...
To split listbots into groups is very common and of
course the mails/posts should be threaded.
I have:
`gnus-sort-gathered-threads-function' is gnus-thread-sort-by-number
`gnus-thread-sort-functions' is (gnus-thread-sort-by-number)
which I didn't configure.
In the help for `gnus-thread-sort-functions', it says:
You should probably always include
`gnus-thread-sort-by-number' in the list of sorting
functions -- preferably first. Also note that
sorting by date is often much slower than sorting
by number, and the sorting order is very
similar. (Sorting by date means sorting by the time
the message was sent, sorting by number means
sorting by arrival time.
The result looks like this:
http://user.it.uu.se/~embe8573/dumps/gnus-group-mailing-list-threads.png
I think that is the standard look with respect to
sorting, because, as I said, I didn't configure that.
Compared to that, (what I can see) group threads by
subject, within those by time (actually number), with
the most recent last - compared to that, what is it you
would like to you change? (You probably already wrote
that but it was hard to make out with all the other
material you provided.)
--
underground experts united
next parent reply other threads:[~2014-07-27 22:55 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 [this message]
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
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=87ha225s3m.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).