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=-0.5 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, RCVD_IN_DNSWL_LOW,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 5814 invoked from network); 3 Jul 2023 04:09:19 -0000 Received: from mx1.math.uh.edu (129.7.128.32) by inbox.vuxu.org with ESMTPUTF8; 3 Jul 2023 04:09:19 -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) (envelope-from ) id 1qGAsG-0074uD-1G for ml@inbox.vuxu.org; Sun, 02 Jul 2023 23:09:16 -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) (envelope-from ) id 1qGAsF-002KwO-2J for ml@inbox.vuxu.org; Sun, 02 Jul 2023 23:09:15 -0500 Received: from mx2.math.uh.edu ([129.7.128.33]) by lists1.math.uh.edu with esmtp (Exim 4.96) (envelope-from ) id 1qGAsD-002KwF-0G for ding@lists.math.uh.edu; Sun, 02 Jul 2023 23:09:13 -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) (envelope-from ) id 1qGAsB-0042QX-1r for ding@lists.math.uh.edu; Sun, 02 Jul 2023 23:09:12 -0500 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=X2qB757TGcOVQ0WiV2pOLEtHHLVybos071a266kJ66c=; b=Wt7WnSuB+rL51YLSv1gdZHmwR5 V+ohdJATpvGvJDQr3yvYFAhXqOw3Y60/8+3aLx683VZ0wvsWfPvEZkic7ilmMbwaOTDh6UVyXVhDe OKJwQgIBsPnuMgz7aGzqK/cFHvXyCHsrxp9l27Gj6ZLYCUVdzlMX1EYuSB1swzeumkLY=; 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 1qGAs3-0004h1-9I for ding@gnus.org; Mon, 03 Jul 2023 06:09:06 +0200 Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1qGAs0-00018i-GK for ding@gnus.org; Mon, 03 Jul 2023 06:09:00 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: ding@gnus.org From: Eric Abrahamsen Subject: Re: help with corrupted files; ticked articles missing Date: Sun, 02 Jul 2023 21:08:52 -0700 Message-ID: <875y71skkr.fsf@ericabrahamsen.net> References: <0qr0pqzkmg.fsf@mirror.to> Mime-Version: 1.0 Content-Type: text/plain User-Agent: Gnus/5.13 (Gnus v5.13) Cancel-Lock: sha1:3rUCAVSXnIg3uWChNei4th11ELQ= List-ID: Precedence: bulk akb+lists.ding@mirror.to (Andrew B) writes: > The partition containing my home directory filled up, and I cleared > space and exited gnus, though I am not sure in what order. > > At present, when I start gnus, the group that I was reading > when the disk filled up has a Group buffer line like this: > 3: 2 / 1! 124410: nnimap+machinename:INBOX > > but it should look more like this: > 3: 80 / 997! 124410: nnimap+machinename:INBOX > > When I enter the group, no matter how many articles I tell gnus to > fetch, it only shows those two unread articles. The read articles > are still on the server, gnus just won't fetch and display them. With nnimap groups, it can often work to use "M-g" on the group in question, which can help refresh Gnus' understanding of read counts from the server. That's the first thing I'd try.