From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Deus Max Newsgroups: gmane.emacs.bugs Subject: bug#39618: 28.0.50; gnus nnimap reports more group articles than actually exist Date: Wed, 19 Feb 2020 22:06:59 +0200 Message-ID: <871rqqwdcs.fsf@aia00054aia.gr> References: <877e0nlkk6.fsf@aia00054aia.gr> <875zg6kuue.fsf@ericabrahamsen.net> <877e0jwtx8.fsf@aia00054aia.gr> <87eeur4lxk.fsf@ericabrahamsen.net> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="9441"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: 39618@debbugs.gnu.org To: Eric Abrahamsen Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Wed Feb 19 21:08:37 2020 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1j4Ve8-0002I1-CQ for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 19 Feb 2020 21:08:36 +0100 Original-Received: from localhost ([::1]:59468 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1j4Ve6-0001ec-UI for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 19 Feb 2020 15:08:35 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:46852) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1j4Vdb-0001eW-Kv for bug-gnu-emacs@gnu.org; Wed, 19 Feb 2020 15:08:04 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1j4Vda-0003O5-6R for bug-gnu-emacs@gnu.org; Wed, 19 Feb 2020 15:08:03 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:37439) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1j4VdZ-0003Nr-Vy for bug-gnu-emacs@gnu.org; Wed, 19 Feb 2020 15:08:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1j4VdZ-0002cO-Qj for bug-gnu-emacs@gnu.org; Wed, 19 Feb 2020 15:08:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Deus Max Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 19 Feb 2020 20:08:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 39618 X-GNU-PR-Package: emacs Original-Received: via spool by 39618-submit@debbugs.gnu.org id=B39618.158214284410006 (code B ref 39618); Wed, 19 Feb 2020 20:08:01 +0000 Original-Received: (at 39618) by debbugs.gnu.org; 19 Feb 2020 20:07:24 +0000 Original-Received: from localhost ([127.0.0.1]:43412 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1j4Vcy-0002bJ-G7 for submit@debbugs.gnu.org; Wed, 19 Feb 2020 15:07:24 -0500 Original-Received: from mout.gmx.net ([212.227.17.20]:39155) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1j4Vcw-0002b2-1u for 39618@debbugs.gnu.org; Wed, 19 Feb 2020 15:07:22 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1582142826; bh=vCkh1wcFai34QUUkjzjYWzHvxNERmRVdo7dEZzeJiKI=; h=X-UI-Sender-Class:From:To:Cc:Subject:References:Date:In-Reply-To; b=Shx+UxtzyiO6YCD1Janzv63GSG0Zs5zoWDpJSm0fmgtr/viZT9XFoWqC8Oyc8EgO1 MGq3uVKOsHSPi3vx+00L42XS+wGdV9XhFwX6eLBRmxWNh3IUzYX2NuiWBa7tQVye86 uAFc7ZGxt9R1cOMMKBI/pQRQgM//9losoxLNAZBo= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Original-Received: from dellcorei5dias ([5.54.155.167]) by mail.gmx.com (mrgmx105 [212.227.17.174]) with ESMTPSA (Nemesis) id 1MowKc-1jo2i73ZU6-00qRlp; Wed, 19 Feb 2020 21:07:06 +0100 In-Reply-To: <87eeur4lxk.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Tue, 18 Feb 2020 13:36:55 -0800") X-Provags-ID: V03:K1:3EtrEkRlfculc45s/+76x/ErdKf+6zbFDR+p1UW8/v4fxSYf7PA 0Wy/qrETHJK7XGg8VkLcc1Z5qhzlBj+zRUJ82fZB1lJZg1tnl1XJN0/uRtxCJGuHu6XAU+g PJDgYzFOApI1Fqit+1K/oO7C2OSi9r7mWpQjiNJBWQ4NUW5DwkX+EEjgEBP0AITIozSrMnY P6eno9J0SK9uQJNfx0wmg== X-UI-Out-Filterresults: notjunk:1;V03:K0:PHbtKt6h3wE=:ERpyHyaBa/vhLQXuirFhB/ cWvu0ukZAnzeSS2FXL3LYmBKCDdDF+i2RHlnmZ0Kva1xeew0kqC0ktigfgHcZXjIWlaHCwWEQ 7A5XjTsmgBKxUHYqzZvAHpQbTR37z4+KyF5RL33ECre5W1Rjf6aYCsoE48bWQqD7JCun7p7ka hsNv4qGFAS74/lyW9Ix2Pm3UZg0bfgQEiO6MJBJ0LAeD/d5lbeWENlau3tpAGx/br9cqWHZmK KaExNqOdH0DSRJXVr3W852xC3XXYDr7xo5HhNmB+Fmeb7JjXSW24nS6/F0Tu1HQbwbMwkooDu J/gZ/nR9cohzH1Zg6xnVqHYc1Fd9nBkqZqGCK3AjUSWFGQDmlskLOz2pRI+UOW7lGp8jANhUG LxJhwRHdZda+wrxgpkB+y28D5cbjl2iEatoxzXDWKkCIQZJHtwGEE2glcVw6se8tFyZNVBQub QFAupm1CzPoZu2uG15phIJCz+zMT0OenhgPRpayQ2OVOMZchTre0xIK+UpUe3CvpinsZcrUKF Fv3lymjhJhheZUjmgY1Qx+jDsXzqdveYfFqn+5i3eiBPWKTyPoDWav7sZo3bvThRggzFqGpNq anmbULjLIB7Dl6cwLWkGVEoho8NT89el3b7LoSkKfeDF5CAdJKckKVRGAJzW0kV8sCOaBKMn5 ryHwhL3RdWKXhWZXk7oOrB7CX1c4M6aysN3ky4HpVUKa8boEOe10IQ0IY+2XmEgYIYD67SiBc a/lqbpI9F+ar8dbH1xAd7dwf34JC2V7+VWXeYG2dAWR/b//HMdAM/Hhulz7Ib42TkpdHyGmv X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 209.51.188.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:176258 Archived-At: On Tue, Feb 18 2020, Eric Abrahamsen wrote: > On 02/18/20 21:56 PM, Deus Max wrote: >> On Sun, Feb 16 2020, Eric Abrahamsen wrote: >> >>> Deus Max writes: >>> >>>> Recently my gnus started displaying (in the *Group* buffer) some groups >>>> (which had previously no unread articles) with an unread "ghost" article >>>> but which groups could not be normally entered. >>>> snip >>>> This issue has happened before, it is not the first time. >>> >>> This definitely happens to many of us from time to time. Unfortunately I >>> can't really reproduce the problem, as by the time it appears it's too >>> late to figure out where it came from, though I assume it has to do with >>> Gnus calculating unread messages from a high-low range, and not being >>> aware of "filled in" read messages within that range. >>> >> You think this is a nnimap or a general Gnus issue ? > > I don't know. I suspect that it's a general Gnus issue, but it is more > evident with nnimap, since that's pretty much the only (?) server where > local marks must be kept in sync with a remote server. In principle, > there's no reason why Gnus would need to keep local marks for imap > groups. > Hey ! Maybe you have a point here. Simplifying nnimap not to keep track of local marks, may not only reduce complexity but also take care of this problem. If it's not needed, it's a waste. What do you think ? Of course, some info needs to be kept to avoid the heavy load that occurs when one starts with an empty .newsrc. For one, we have the group names... >> Understanding how the newsrc file is written, should be next for me. > > It's just, with their lists of marks. The lists are in "gnus range" > format (see gnus-range.el), which is just a compressed list of integers: > '(1 2 3 4 6 12 21 22 23) => '((1. 4) 6 12 (21. 23)) > > They are treated as sets, with lots of the usual set manipulation > functions in gnus-range.el. Part of the problem is the direct > manipulation of ranges that happens elsewhere in the codebase, typically > impenetrable thickets of "(setcdr (nthcdr 3 range) (cadar range)" etc > etc, often with little or no comments. > > On my (long) list of things to do with Gnus is to write several more > macros for range manipulation, so that all the messy stuff happens > inside gnus-range.el, and the rest of the codebase is fairly readable. > My hope is that, in the course of that process, bugs will show > themselves up. > Really interesting, thanks. Sounds like a complete re-write of Gnus (streamlined of course!) is hiding behind what you just said :-) >> The primary thing a mail, em..sorry.. news-reader, should be is stable. >> Not to have any corruption issues. > > No argument here... > >>> In the meantime, is "M-g" on the problematic group(s) enough to >>> permanently fix the problem? Not a great solution, though better than >>> doctoring your .newsrc.eld file... >> >> No difference. On testing your suggestion, the "M-g" was ignored as >> was/is the regular "g". > > Sorry, I don't know where else to look. My only solution is the hard > one: clean up range manipulation until we can see what's going on. Thanks I didn't find any other similar bug reports on debbugs. Is that just my terrible search abilities ?