From: pmlists@free.fr (Peter Münster)
To: ding@gnus.org
Subject: Re: thread sorting
Date: Tue, 03 May 2011 15:21:27 +0200 [thread overview]
Message-ID: <87y62ndinc.fsf@micropit.couberia.bzh> (raw)
In-Reply-To: <87pqo0ge8a.fsf@member.fsf.org>
[-- Attachment #1: Type: text/plain, Size: 357 bytes --]
Tassilo Horn <tassilo@member.fsf.org> writes:
> | (not gnus-thread-sort-by-most-recent-date)
That's it, thanks!
After reading
"Note that sorting really is normally done by looking only at the
roots of each thread."
I was quite sure, that it would be nearly impossible to do...
Thus, please find attached a little patch for the documentation.
[-- Attachment #2: git.diff --]
[-- Type: text/x-patch, Size: 1573 bytes --]
diff --git a/texi/ChangeLog b/texi/ChangeLog
index c9e56c4..0628e0d 100644
--- a/texi/ChangeLog
+++ b/texi/ChangeLog
@@ -1,3 +1,9 @@
+2011-05-03 Peter Münster <pmlists@free.fr>
+
+ * gnus.texi (Summary Buffer Lines):
+ gnus-summary-user-date-format-alist does not exist.
+ (Sorting the Summary Buffer): More about sorting threads.
+
2011-04-14 Teodor Zlatanov <tzz@lifelogs.com>
* gnus.texi (nnmairix caveats, Setup, Registry Article Refer Method)
diff --git a/texi/gnus.texi b/texi/gnus.texi
index e414508..b458ce6 100644
--- a/texi/gnus.texi
+++ b/texi/gnus.texi
@@ -4953,7 +4953,7 @@ Download mark.
Desired cursor position (instead of after first colon).
@item &user-date;
Age sensitive date format. Various date format is defined in
-@code{gnus-summary-user-date-format-alist}.
+@code{gnus-user-date-format-alist}.
@item u
User defined specifier. The next character in the format string should
be a letter. Gnus will call the function
@@ -7340,7 +7340,9 @@ predicate functions include @code{gnus-thread-sort-by-number},
Each function takes two threads and returns non-@code{nil} if the first
thread should be sorted before the other. Note that sorting really is
-normally done by looking only at the roots of each thread.
+normally done by looking only at the roots of each thread. Exceptions
+to this rule are @code{gnus-thread-sort-by-most-recent-number} and
+@code{gnus-thread-sort-by-most-recent-date}.
If you use more than one function, the primary sort key should be the
last function in the list. You should probably always include
[-- Attachment #3: Type: text/plain, Size: 22 bytes --]
--
Peter
next prev parent reply other threads:[~2011-05-03 13:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-03 7:16 Peter Münster
2011-05-03 12:28 ` Tassilo Horn
2011-05-03 13:21 ` Peter Münster [this message]
2011-05-03 18:04 ` Tassilo Horn
2011-05-03 20:45 ` Reiner Steib
2011-05-04 6:32 ` Tassilo Horn
2011-05-04 7:05 ` Peter Münster
2011-05-04 7:15 ` Tassilo Horn
2011-05-04 7:55 ` David Engster
2011-05-04 10:35 ` Tassilo Horn
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=87y62ndinc.fsf@micropit.couberia.bzh \
--to=pmlists@free.fr \
--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).