From: Jarmo Hurri <jarmo.hurrigarbage@cs.helsinki.fi>
Subject: Re: Simple thread sorting question
Date: Fri, 12 Jan 2007 16:17:28 +0200 [thread overview]
Message-ID: <yup4ejq09vnr.fsf@sbz-32.cs.helsinki.fi> (raw)
In-Reply-To: <v93b6gwmmp.fsf@marauder.physik.uni-ulm.de>
Reiner> I tried again. ... the threads are sorted ascending (WRT the
Reiner> most recent number of a posting in each thread). ... But you
Reiner> may prepend `gnus-summary-line-format' with "%N" for
Reiner> debugging.
Yes, your threads seem to be in correct order. I tried this and the
last lines of my mail threads look like this:
3953 A [ 82: Johannes Schmidt ] Re: CNS - project work available
3964 < 76: Johannes Schmidt >
3963 [ 17: Harri Valpola ] Re: Cortical maps
3965 A [ 30: Harri Valpola ] Re: Tulokset
3972 [ 4: -> Jarmo Hurri ]
As far as I have understood, the first and second thread should be in
reverse order, right? And my ordering seems to follow the number of
the first mail in the thread.
The values of my variables are
`gnus-show-threads'
Value: t
`gnus-thread-sort-functions'
Value: ((not gnus-thread-sort-by-most-recent-number))
`gnus-version'
Value: "Gnus v5.10.8"
If I use the non-reversed sorting, that is, if I set the variable
`gnus-thread-sort-functions'
Value: (gnus-thread-sort-by-most-recent-number)
then the top of the buffer looks like this
3965 A [ 30: Harri Valpola ] Re: Tulokset
3972 [ 4: -> Jarmo Hurri ]
3953 A [ 82: Johannes Schmidt ] Re: CNS - project work available
3964 < 76: Johannes Schmidt >
3963 [ 17: Harri Valpola ] Re: Cortical maps
so now the ordering is correct
Reiner> Try to reproduce it with a minimal configuration.
I will do this at some point. It might be some weird configuration
somewhere (I have inherited a few XEmacs settings...), but if this is
the case then something might be at least missing from the manual.
BTW, how do you get the following neat elisp evaluation buffer
started:
Reiner> | ELISP> gnus-summary-line-format
--
Jarmo Hurri
Commercial email countermeasures included in header email
address. Remove all garbage from header email address when replying,
or just use firstname.lastname@cs.helsinki.fi .
next prev parent reply other threads:[~2007-01-12 14:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-11 17:49 Jarmo Hurri
2007-01-11 21:06 ` Reiner Steib
2007-01-12 7:10 ` Jarmo Hurri
2007-01-12 10:43 ` Reiner Steib
2007-01-12 14:17 ` Jarmo Hurri [this message]
2007-01-12 17:05 ` Reiner Steib
2007-01-13 10:37 ` Jarmo Hurri
2007-01-13 12:13 ` orphaned articles / loose threads and gnus-thread-sort-by-most-recent-number (was: Simple thread sorting question) Reiner Steib
[not found] ` <mailman.3033.1168717393.2155.info-gnus-english@gnu.org>
2007-01-15 8:15 ` orphaned articles / loose threads and gnus-thread-sort-by-most-recent-number Jarmo Hurri
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=yup4ejq09vnr.fsf@sbz-32.cs.helsinki.fi \
--to=jarmo.hurrigarbage@cs.helsinki.fi \
/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).