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=-1.9 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 Received: from mx1.math.uh.edu (mx1.math.uh.edu [129.7.128.32]) by inbox.vuxu.org (Postfix) with ESMTP id 2FB8722B27 for ; Mon, 29 Jan 2024 02:20:54 +0100 (CET) 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.97.1) (envelope-from ) id 1rUGKT-00000001Jki-0xez for ml@inbox.vuxu.org; Sun, 28 Jan 2024 19:20:53 -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 1rUGKS-00000003yLy-23FP for ml@inbox.vuxu.org; Sun, 28 Jan 2024 19:20:52 -0600 Received: from mx1.math.uh.edu ([129.7.128.32]) by lists1.math.uh.edu with esmtp (Exim 4.97.1) (envelope-from ) id 1rUGKR-00000003yLs-0Z5C for ding@lists.math.uh.edu; Sun, 28 Jan 2024 19:20:51 -0600 Received: from quimby.gnus.org ([95.216.78.240]) by mx1.math.uh.edu with esmtps (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.97.1) (envelope-from ) id 1rUGKP-00000001JkB-4AvB for ding@lists.math.uh.edu; Sun, 28 Jan 2024 19:20:51 -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=cfiXpIP29/SaowpMT+eeeWkBkiOhW6/ci7QDMjsy5SE=; b=pOqKl4UcKXsMjav1D8Rr+v4nFA +10hlWQCgF3trQmsaB/NQeYR8e0LWgyc8TojpXr+/Gz+o+sE/e9wpjZw9rmA9pQfvzVgzs+5NBLUO OA1vm3kjDYcy6OI1Hq8+5t7uHiRNF+ydxRh37YTUm2y2ypKJPTMSJ/pu+etmG1bBpOFw=; 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 1rUGKE-0001Qv-Id for ding@gnus.org; Mon, 29 Jan 2024 02:20:40 +0100 Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1rUGKD-0009Ig-Ur for ding@gnus.org; Mon, 29 Jan 2024 02:20:37 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: ding@gnus.org From: Eric Abrahamsen Subject: Re: How to display dormant articles in a summary buffer? Date: Sun, 28 Jan 2024 17:20:28 -0800 Message-ID: <87y1c9kk9v.fsf@ericabrahamsen.net> References: <87o7d9do4x.fsf@dod.no> <87plxld6pi.fsf@dataswamp.org> <87r0i1cdjc.fsf@dod.no> Mime-Version: 1.0 Content-Type: text/plain User-Agent: Gnus/5.13 (Gnus v5.13) Cancel-Lock: sha1:8eA3Ew9eyf7YAcNVzmdRm43Bqr4= List-ID: Precedence: bulk Steinar Bang writes: >>>>>> Emanuel Berg : > >> Steinar Bang wrote: >>> Today I wanted to find this one, which I knew was residing >>> as a dormant article (and thread) [...] > >> What is a dormant article? > > If you use '?' in the summary buffer the article will be hidden next > time you open the summary buffer... unless there has been a reply to the > article, in which case the dormant article(s) will become visibile. > > So if you have a thread of dormant articles and there is a reply to the > latest article, the entire thread will become visible when you enter the > Summary buffer. That seems like the exact behavior you get with plain old read articles, though, doesn't it? (I also have never really known what "dormant" meant.)