From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=0.4 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.4 Received: from mx2.math.uh.edu (mx2.math.uh.edu [129.7.128.33]) by inbox.vuxu.org (Postfix) with ESMTP id 5C8922B1A7 for ; Sat, 17 Feb 2024 18:34:13 +0100 (CET) Received: from lists1.math.uh.edu ([129.7.128.208]) by mx2.math.uh.edu with esmtps (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.97.1) (envelope-from ) id 1rbOZn-0000000Bl3W-1P3v for ml@inbox.vuxu.org; Sat, 17 Feb 2024 11:34:11 -0600 Received: from lists1.math.uh.edu ([127.0.0.1] helo=lists.math.uh.edu) by lists1.math.uh.edu with smtp (Exim 4.97.1) (envelope-from ) id 1rbOZn-00000000cc4-0MMJ for ml@inbox.vuxu.org; Sat, 17 Feb 2024 11:34:11 -0600 Received: from mx2.math.uh.edu ([129.7.128.33]) by lists1.math.uh.edu with esmtp (Exim 4.97.1) (envelope-from ) id 1rbOZl-00000000cby-2hMf for ding@lists.math.uh.edu; Sat, 17 Feb 2024 11:34:09 -0600 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.97.1) (envelope-from ) id 1rbOZZ-0000000Bl2n-3JNg for ding@lists.math.uh.edu; Sat, 17 Feb 2024 11:34:09 -0600 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnus.org; s=20200322; h=Content-Type:Mime-Version:References:Message-ID:Date:Subject: From:To:Sender:Reply-To:Cc:Content-Transfer-Encoding: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=VqVXrbWPwDQ0K1OiaD/oko/OsYgpowAoHyGPRZDP8D0=; b=Hs/g1yH8Z0DsyWoGLFHUtFyBg5 FTheJDAiAeODkI+WNR6IJUUBQnHuPxc7NCuUypImzPoEpxD5f+x3du8Xh2WVzLiTRlq7pL2rF9MP9 GUNRipKXp8XDlOJhCZTadeC50By8GcMFnH0+IR/LQlHpvjoCc+rzH7oBQnDfBXQYdrAU=; 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 1rbOZC-0004k5-1v for ding@gnus.org; Sat, 17 Feb 2024 18:33:36 +0100 Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1rbOZA-0009At-D8 for ding@gnus.org; Sat, 17 Feb 2024 18:33:32 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: ding@gnus.org From: Eric Abrahamsen Subject: Re: Display all messages, including read ones Date: Sat, 17 Feb 2024 09:33:19 -0800 Message-ID: <87plwvq9ls.fsf@ericabrahamsen.net> References: <18763.5332507611$1708185440@news.gmane.org> Mime-Version: 1.0 Content-Type: text/plain User-Agent: Gnus/5.13 (Gnus v5.13) Cancel-Lock: sha1:rdmDs0vCPL94gMU/pExVUZcL0Vg= List-ID: Precedence: bulk Husain Alshehhi writes: > Hello, > > When there is an unread message in a long thread, the group buffer will > indicate that there is an unread message. When I press to visit > that group, the cursor will show that message. But often, in a long > thread, gnus will not show the whole thread, even thoug the parameters > > (display . all) > > is configured on the group: only the root, and the last few messages > appear. Even when pressing "A T" (gnus-summary-refer-thread) I still do > not get some of the old, unexpired read messages. They do not show up > even when I visit the root and press "T s" (gnus-summary-show-thread) I > still do not get the thread. > > What I expected was that I would be able to see all the message in the > thread when I visit the unread message. > > However, if in the group buffer I press C-u (which prompts me to > enter the number of messages to display), only then I see all the > messages in thread, which also includes expired ones. > > I am not clear why gnus behaves this way. It would be great if someone > can help me root cause this issue. Possibly relevant configs I have: > > gnus-show-threads: t > gnus-refer-thread-limit: 500 This last option does what it says, so if your threads are longer than this, "A T" will not show you all the messages. "T s" only reveals messages that happen to be hidden for some reason, it won't load messages that aren't already present in the Summary buffer, so that same thread limit will stay in effect. The only weird one is (display . all), which I would have assumed would load all messages, like it says.