From: David Z Maze <dmaze@mit.edu>
Subject: Re: Moving an article within summary buffer
Date: Tue, 27 Sep 2005 13:56:00 -0400 [thread overview]
Message-ID: <y688xxi9yz3.fsf@mass-toolpike.mit.edu> (raw)
In-Reply-To: <1127840435.675787.304520@o13g2000cwo.googlegroups.com>
romeomedina@libero.it writes:
> I put in ~/.gnus.el:
>
> (setq gnus-thread-sort-functions
> '(gnus-thread-sort-by-date))
>
> , but for some strange reason sorting is still done
> on article numbers and not on date, when articles
> have the same subject. How on earth do I fix that?
Are you using threading? info://gnus/Sorting+the+Summary+Buffer
mentions that, if you're not, you need to use
gnus-article-sort-functions and gnus-article-sort-by-date, etc.,
instead. Also note the comment that you probably want
gnus-{article,thread}-sort-by-number at the front of the list to get a
consistent sort in case two articles have the same date.
--dzm
next prev parent reply other threads:[~2005-09-27 17:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-27 9:03 romeomedina
2005-09-27 11:49 ` Adam Sjøgren
2005-09-27 17:00 ` romeomedina
2005-09-27 17:56 ` David Z Maze [this message]
2005-09-27 19:54 ` romeomedina
2005-09-27 20:51 ` Reiner Steib
2005-09-28 8:45 ` romeomedina
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=y688xxi9yz3.fsf@mass-toolpike.mit.edu \
--to=dmaze@mit.edu \
/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).