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.8 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL 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 319A4217CA for ; Sun, 21 Apr 2024 18:18:42 +0200 (CEST) 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 1ryZte-00000002VuJ-3J4s for ml@inbox.vuxu.org; Sun, 21 Apr 2024 11:18:35 -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.97.1) (envelope-from ) id 1ryZte-00000003fpo-2OTk for ml@inbox.vuxu.org; Sun, 21 Apr 2024 11:18:30 -0500 Received: from mx1.math.uh.edu ([129.7.128.32]) by lists1.math.uh.edu with esmtp (Exim 4.97.1) (envelope-from ) id 1ryZtb-00000003fpf-3pnR for ding@lists.math.uh.edu; Sun, 21 Apr 2024 11:18:27 -0500 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 1ryZtZ-00000002Vtq-28Pz for ding@lists.math.uh.edu; Sun, 21 Apr 2024 11:18:27 -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=2T2VcsFKvn2fR5iFG/pFbfJ/jbb+YRsRHJXYgpyjVBc=; b=bfQw18jlQBQhuGPeh45NZIkzmS 1wSlGeUqGnvxjFQFlvJWB6MlQbrg69ASl0+9Q+jQhhcTAj7Xkua1kgF0LxtD5HLwYn8vP8jAHAHCb 6FAT4I/19X/eXd8R772fbgnbKLJCjVfN1BhgwmAmhlHUO/7TZnUzSYuNnIIhQ9nG2XZs=; 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 1ryZtS-0007eH-OX for ding@gnus.org; Sun, 21 Apr 2024 18:18:21 +0200 Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1ryZtO-000773-LW for ding@gnus.org; Sun, 21 Apr 2024 18:18:14 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: ding@gnus.org From: Eric Abrahamsen Subject: Re: Gnus sometimes reports new messages but not showing them on IMAP server Date: Sun, 21 Apr 2024 09:18:07 -0700 Message-ID: <875xwalmf4.fsf@ericabrahamsen.net> References: <87h6g7mm8r.fsf@debian-hx90.lan> <878r1blqcg.fsf@uwo.ca> <87ttjx55ey.fsf@uwo.ca> 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:BVhYl24voSV7BTMPh3FzIhtrzmY= List-ID: Precedence: bulk Arash Esbati writes: > Dan Christensen writes: > >> Neither of those does the full resync that `M-g' does for IMAP groups. > > I can confirm this. > >> I don't know what is going on behind the scenes, but `M-g' is necessary >> for me to see up-to-date information sometimes. > > I haven't tried to read/understand the code, but in the Group buffer, > neither 'g' nor 'C-u g' does what 'M-g' does inside the Summary buffer > of an IMAP group. And I would have expected that 'C-u g' in Group > buffer fits the bill: > > ,----[ C-h f gnus-group-get-new-news RET ] > | gnus-group-get-new-news is an autoloaded interactive subr-native-elisp > | in ‘gnus-group.el’. > | > | (gnus-group-get-new-news &optional ARG ONE-LEVEL) > | > | Get newly arrived articles. > | If ARG is a number, it specifies which levels you are interested in > | re-scanning. If ARG is non-nil and not a number, this will force > | "hard" re-reading of the active files from all servers. > | If ONE-LEVEL is not nil, then re-scan only the specified level, > | otherwise all levels below ARG will be scanned too. > | > `---- > > Hopefully Eric can shed some light on this. This is a long-standing bug, probably the most annoying thing about nnimap. I've made a few attempts at it over the years, but so far haven't been successful. I believe what it comes down to is that "M-g" dumps Gnus' "active" number and re-reads it from the IMAP server, while regular "g" incrementally modifies the active number based on newest changes. So if anything goes wrong with Gnus' active number, errors will accumulate from that point until the user does "M-g". I've focused on figuring out why the active number goes wrong, but in the interest of pragmatism it might be better just to make sure that nnimap always does the equivalent of "M-g" at Gnus startup.