From: jidanni@jidanni.org
To: ding@gnus.org
Subject: thread sorting when no References
Date: Tue, 19 Feb 2008 01:01:39 +0800 [thread overview]
Message-ID: <87pruub3m4.fsf@jidanni.org> (raw)
Gentlemen, it is a ho hum day on say gmane.mail.spam.spamassassin.general
O 3 080218 34||Agnello GeorgeN:spamassassin on VPS ( fedora 7 )
O 1 080218107||Michael ScheidN:
O 1 080218 18||Matus UHLAR - N:
! 2 080218 83||comparity I:Bayes: What am I missing
! 1 080217 82||comparity I:
O 4 080218 15||ItsMikeE I:"Nice girl like to chat" spam
O 1 080218 37||ram I:
O 2 080218 77||Chris I:
OA 1 080218 54||ram I:
But hark, there where I have marked the two messages from comparity,
we see the older message (080217) is nested underneath the newer (080218).
And so reveals a basic flaw of gnus: messages with
the same subject but no interconnecting references will get listed out
of order. The correct order should be the most inner thread has the
most latest discussion. Here we see gnus tricks the user into clicking
the older message! I didn't mess with the Gnus v5.11 defaults:
$ wget -O - http://jidanni.org/comp/.gnus.el |
grep sort|grep -v '^;'|wc -l
0
reply other threads:[~2008-02-18 17:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87pruub3m4.fsf@jidanni.org \
--to=jidanni@jidanni.org \
--cc=ding@gnus.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).