From: Jack Vinson <vinson@unagi.cis.upenn.edu>
Subject: Re: gnus-summary-make-false-root 'adopt
Date: 28 Jul 1999 15:34:33 -0500 [thread overview]
Message-ID: <wkvhb4344m.fsf@chevax.ecs.umass.edu> (raw)
In-Reply-To: Kai =?iso-8859-1?q?Gro=DFjohann's?= message of "16 Jul 1999 23:12:46 +0200"
> Jack Vinson <vinson@unagi.cis.upenn.edu> writes:
JV> However, with one of my mailing lists that I get in digest mode, the
JV> messages are collected in reverse order in the Digest. As a result, the
JV> actual thread head is /after/ the replies when I open the digest. As a
JV> result, Gnus simply makes one of the replies the adopted parent.
I've discovered the source of the problem I am having. The real solution
is to create a new variable with a name like
gnus-thread-gathered-threads-sort-functions which is similar to
gnus-thread-sort-functions.
This function is defined in gnus-sum:
(defun gnus-sort-gathered-threads (threads)
"Sort subtreads inside each gathered thread by article number."
(let ((result threads))
(while threads
(when (stringp (caar threads))
(setcdr (car threads)
(sort (cdar threads) 'gnus-thread-sort-by-number)))
(setq threads (cdr threads)))
result))
Obviously, each subthread is sorted by its article number. If I change
this to sort by date, then my specific problem disappears.
Is a new variable even useful here, or should I just make the change in my
own code?
--
Jack Vinson
Zippy: I haven't been married in over six years, but we had sexual counseling
every day from Oral Roberts!!
prev parent reply other threads:[~1999-07-28 20:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-17 19:43 Jack Vinson
1999-07-16 21:12 ` Kai Großjohann
1999-07-27 16:27 ` Jack Vinson
1999-07-27 12:26 ` Kai Großjohann
1999-07-28 20:34 ` Jack Vinson [this message]
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=wkvhb4344m.fsf@chevax.ecs.umass.edu \
--to=vinson@unagi.cis.upenn.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).