From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <ding-owner+M39659=ml=inbox.vuxu.org@lists.math.uh.edu>
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 5EDA727409
	for <ml@inbox.vuxu.org>; Mon, 29 Jan 2024 12:24:50 +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 <ding-owner+M39659=ml=inbox.vuxu.org@lists.math.uh.edu>)
	id 1rUPko-00000001bo7-1wfr
	for ml@inbox.vuxu.org;
	Mon, 29 Jan 2024 05:24:47 -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 <ding-owner+M39659=ml=inbox.vuxu.org@lists.math.uh.edu>)
	id 1rUPko-00000003zfJ-0ccQ
	for ml@inbox.vuxu.org;
	Mon, 29 Jan 2024 05:24:42 -0600
Received: from mx1.math.uh.edu ([129.7.128.32])
	by lists1.math.uh.edu with esmtp (Exim 4.97.1)
	(envelope-from <ding-account@m.gmane-mx.org>)
	id 1rUPkm-00000003zfC-1PQ1
	for ding@lists.math.uh.edu;
	Mon, 29 Jan 2024 05:24:40 -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 <ding-account@m.gmane-mx.org>)
	id 1rUPkj-00000001bnd-1KJZ
	for ding@lists.math.uh.edu;
	Mon, 29 Jan 2024 05:24:40 -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=WJ9XZakTiTQ/MCAir5rCpom+W4e6m5wcezpE4oLD+Aw=; b=PFH2xyDN10gbwhZG8VdAWQe1fq
	wpKjFQXKJEMDTmxtriX++Fc3XKdUrasDyqFGcQP9JHWFK4PgGKr14Xy4ffbg4eNklhza7YNNNxuQx
	SKjyTJBLbfI/gx1fYzjxMMvnNOHbkZ4ghJVn1dUnuJTZkmlgGa5b7EHm3ZuWvgFnNMa4=;
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 <ding-account@m.gmane-mx.org>)
	id 1rUPkc-0006Xk-8e
	for ding@gnus.org; Mon, 29 Jan 2024 12:24:32 +0100
Received: from list by ciao.gmane.io with local (Exim 4.92)
	(envelope-from <ding-account@m.gmane-mx.org>)
	id 1rUPka-0006nK-Rg
	for ding@gnus.org; Mon, 29 Jan 2024 12:24:28 +0100
X-Injected-Via-Gmane: http://gmane.org/
Mail-Followup-To: ding@gnus.org
To: ding@gnus.org
From: Steinar Bang <sb@dod.no>
Subject: Re: How to display dormant articles in a summary buffer?
Date: Mon, 29 Jan 2024 12:24:22 +0100
Organization: Probably a good idea
Message-ID: <yqoonklil3cjsbd.fsf@dod.no>
References: <87o7d9do4x.fsf@dod.no> <87plxld6pi.fsf@dataswamp.org>
	<87r0i1cdjc.fsf@dod.no> <87y1c9kk9v.fsf@ericabrahamsen.net>
Mime-Version: 1.0
Content-Type: text/plain
User-Agent: Gnus/5.13 (Gnus v5.13)
Cancel-Lock: sha1:MXwlT1oTwqCcVF+OXhH51vH3FFY=
Mail-Copies-To: never
List-ID: <ding.gnus.org>
Precedence: bulk

>>>>> Eric Abrahamsen <eric@ericabrahamsen.net>:

> 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.)

Dormant articles stay hidden until you get a reply, so they don't
clutter up your summary buffer the way ticked articles do.

Read articles just stay hidden when you get a reply, you have to use ^
to see the articles replied to.