From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/32023 Path: main.gmane.org!not-for-mail From: prj@po.cwru.edu (Paul Jarc) Newsgroups: gmane.emacs.gnus.general Subject: Re: What does `gathering loose threads' mean? Date: 09 Aug 2000 12:17:43 -0400 Sender: owner-ding@hpc.uh.edu Message-ID: References: NNTP-Posting-Host: coloc-standby.netfonds.no X-Trace: main.gmane.org 1035168365 17461 80.91.224.250 (21 Oct 2002 02:46:05 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 21 Oct 2002 02:46:05 +0000 (UTC) Return-Path: Original-Received: from fisher.math.uh.edu (fisher.math.uh.edu [129.7.128.35]) by mailhost.sclp.com (Postfix) with ESMTP id 3CF58D051E for ; Wed, 9 Aug 2000 12:18:33 -0400 (EDT) Original-Received: from sina.hpc.uh.edu (lists@Sina.HPC.UH.EDU [129.7.3.5]) by fisher.math.uh.edu (8.9.1/8.9.1) with ESMTP id LAC15555; Wed, 9 Aug 2000 11:18:08 -0500 (CDT) Original-Received: by sina.hpc.uh.edu (TLB v0.09a (1.20 tibbs 1996/10/09 22:03:07)); Wed, 09 Aug 2000 11:17:21 -0500 (CDT) Original-Received: from mailhost.sclp.com (postfix@66-209.196.61.interliant.com [209.196.61.66] (may be forged)) by sina.hpc.uh.edu (8.9.3/8.9.3) with ESMTP id LAA14038 for ; Wed, 9 Aug 2000 11:17:12 -0500 (CDT) Original-Received: from multivac.student.cwru.edu (multivac.STUDENT.CWRU.Edu [129.22.239.69]) by mailhost.sclp.com (Postfix) with SMTP id 7458BD051E for ; Wed, 9 Aug 2000 12:17:44 -0400 (EDT) Original-Received: (qmail 7663 invoked by uid 500); 9 Aug 2000 16:17:43 -0000 Mail-Followup-To: ding@gnus.org Original-To: ding@gnus.org In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Wed, 9 Aug 2000 18:00:48 +0200" Original-Lines: 40 X-Mailer: Gnus v5.7/Emacs 20.7 Precedence: list X-Majordomo: 1.94.jlt7 Xref: main.gmane.org gmane.emacs.gnus.general:32023 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:32023 Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai =?iso-8859-1?q?Gro=DFjohann?=) writes: > If I have two messages with the same subject (but otherwise > unrelated), they will be displayed near to each other in the summary > buffer. > > Where does this come from? Testing whether two articles are in the same thread is controlled by the variable gnus-summary-thread-gathering-function. Loose threads are a somewhat separate matter, regarding the sorting of articles within a thread, IIUC. > This lead me to thinking that Gnus looks at the References header of > message 1 and at the References header of message 2 and if MsgId foo > occurs in both headers, then the two messages are in the same > thread. If that's what you want, you can do: (setq gnus-summary-thread-gathering-function 'gnus-gather-threads-by-references) By default, it's set to gnus-gather-threads-by-subject. > Maybe the documentation should be changed to more explicitly point out > that loose threads gathering does NOT look at the References header, > but ONLY at the Subject header. gnus-summary-thread-gathering-function is documented at the end of the `Loose Threads' node. > What is the minimum configuration that will do loose threads > gathering? (I think it is sufficient to set > gnus-summary-make-false-root to a non-nil value, but I'm not sure.) That controls the insertion of dummy lines for missing articles in the thread. If you just want articles with common References: to be in the same thread, without filling in gaps with dummy lines, then setting gnus-summary-thread-gathering-function should suffice. paul