From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-2.1 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 12846 invoked from network); 25 Oct 2023 02:24:30 -0000 Received: from mx1.math.uh.edu (129.7.128.32) by inbox.vuxu.org with ESMTPUTF8; 25 Oct 2023 02:24:30 -0000 Received: from lists1.math.uh.edu ([129.7.128.208]) by mx1.math.uh.edu with esmtps (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.96.1) (envelope-from ) id 1qvTZL-004tYC-0s for ml@inbox.vuxu.org; Tue, 24 Oct 2023 21:24:27 -0500 Received: from lists1.math.uh.edu ([127.0.0.1] helo=lists.math.uh.edu) by lists1.math.uh.edu with smtp (Exim 4.96.1) (envelope-from ) id 1qvTZK-000Lt6-1Y for ml@inbox.vuxu.org; Tue, 24 Oct 2023 21:24:26 -0500 Received: from mx2.math.uh.edu ([129.7.128.33]) by lists1.math.uh.edu with esmtp (Exim 4.96.1) (envelope-from ) id 1qvTZJ-000Lt0-09 for ding@lists.math.uh.edu; Tue, 24 Oct 2023 21:24:25 -0500 Received: from quimby.gnus.org ([95.216.78.240]) by mx2.math.uh.edu with esmtps (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.96.1) (envelope-from ) id 1qvTZB-00527I-2D for ding@lists.math.uh.edu; Tue, 24 Oct 2023 21:24:24 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnus.org; s=20200322; h=Content-Transfer-Encoding:Content-Type:Mime-Version:References :Message-ID:Date:Subject:From:To:Sender:Reply-To:Cc:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:In-Reply-To:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=CBy+TGkAC6uQKiJmG5K1KoNvUiNMzM7H9e9aTwV1bmU=; b=Jk6Zl+46AKfUc0hQK4VPnl2p6C TIJkq4yDIy4IAMa1CU3zXy+PTTY5RONRu0LstVajx8a+/FifsI72tsNczYybZY0ONO/2gHhuXhiOY /rq4TYVUbpF6aGBYYqc++JAD1z1G5jmfHkGlRmnfsF6rDWxsB3zP+qFcCQm9hEv4hmzs=; Received: from ciao.gmane.io ([116.202.254.214]) by quimby.gnus.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1qvTYw-0002qh-DW for ding@gnus.org; Wed, 25 Oct 2023 04:24:06 +0200 Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1qvTYt-0001Jq-Us for ding@gnus.org; Wed, 25 Oct 2023 04:23:59 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: ding@gnus.org From: Andrew Cohen Subject: Re: Gnus threads too many articles together Date: Wed, 25 Oct 2023 10:23:51 +0800 Message-ID: <87il6v783s.fsf@ust.hk> References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit User-Agent: Gnus/5.13 (Gnus v5.13) Cancel-Lock: sha1:MCo/06fjWQWB/FQHfng+nJBgdxA= List-ID: Precedence: bulk >>>>> "JH" == John Haman writes: [...] JH> I don't know the most informative way to ask this question, but JH> is there a way to make Gnus just thread distinct conversations JH> together (like Outlook.) Do you mean you want to NOT combine messages with the same subject into a thread, but only those that are actually related? ‘gnus-summary-thread-gathering-function’ Gnus gathers threads by looking at ‘Subject’ headers. This means that totally unrelated articles may end up in the same “thread”, which is confusing. An alternate approach is to look at all the ‘Message-ID’s in all the ‘References’ headers to find matches. This will ensure that no gathered threads ever include unrelated articles, but it also means that people who have posted with broken newsreaders won’t be gathered properly. The choice is yours—plague or cholera: ‘gnus-gather-threads-by-subject’ This function is the default gathering function and looks at ‘Subject’s exclusively. ‘gnus-gather-threads-by-references’ This function looks at ‘References’ headers exclusively. If you want to test gathering by ‘References’, you could say something like: (setq gnus-summary-thread-gathering-function 'gnus-gather-threads-by-references) -- Andrew Cohen