From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Karl Fogel Newsgroups: gmane.emacs.devel Subject: Re: Why does Gnus article-moving act like a fetch of new news? Date: Wed, 05 May 2021 18:21:42 -0500 Message-ID: <87eeekpy0p.fsf@red-bean.com> References: <87lf9rruzl.fsf@red-bean.com> <87wnt824dq.fsf@gnus.org> <87eeffsaa6.fsf@ericabrahamsen.net> <87tuobs7xd.fsf@red-bean.com> <87a6q3s6ja.fsf@ericabrahamsen.net> <875z0qextc.fsf@red-bean.com> <87pmyxg81f.fsf@ericabrahamsen.net> <87tunjsfnm.fsf@ericabrahamsen.net> Reply-To: Karl Fogel Mime-Version: 1.0 Content-Type: text/plain; format=flowed Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="8447"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: Lars Ingebrigtsen , Emacs Development To: Eric Abrahamsen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu May 06 01:22:23 2021 Return-path: Envelope-to: ged-emacs-devel@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 1leQqU-00024l-DH for ged-emacs-devel@m.gmane-mx.org; Thu, 06 May 2021 01:22:22 +0200 Original-Received: from localhost ([::1]:34658 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1leQqT-0005Ru-62 for ged-emacs-devel@m.gmane-mx.org; Wed, 05 May 2021 19:22:21 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:35268) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1leQpu-000536-QW for emacs-devel@gnu.org; Wed, 05 May 2021 19:21:46 -0400 Original-Received: from sanpietro.red-bean.com ([45.79.25.59]:38146) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1leQps-0007bQ-PX for emacs-devel@gnu.org; Wed, 05 May 2021 19:21:46 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=red-bean.com; s=202005newsp; h=Content-Type:MIME-Version:Message-ID: In-Reply-To:Date:Reply-To:References:Subject:Cc:To:From:Sender: Content-Transfer-Encoding:Content-ID:Content-Description; bh=Udx1hB9zHGMwzhyTvrxJ9Xa5ly8sMjfKoo/qcZQ/S5I=; t=1620256904; x=1621466504; b=LEAaI7Yu8WijxuMjdAOIxBUqIEQzBnTEauhPDuc/MWDbwFNCfW1c/9JRbPz8bFpUrcpeLaLB3i oSIwI1kvFxjooC5nELZ3Bc0zUeDYKuZozkEjbga4wT1g7AM1n/ObPvTMPo7NU8FbCGG1acKS7twYL dO1KLVIuGJs8LAFnT17VuST0loxA4BNsiRI4nwNg4wYATKc2s1LvUZTrlc7yi7TQx781P0K+HbDMN vSs85PnvPGUzeM1kVBTlgjAJ3Owh2BYKscsOq2f7Tr+vWYe/h2h18zp1ADgRcc6N6UEffxlNo5kYr bLNYSOXFK2wpj8gyjMg1ZElYN4pKAaQU6Htpw==; Original-Received: from [12.106.183.66] (port=55749 helo=kwork) by sanpietro.red-bean.com with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1leQpr-0001Kz-9l; Wed, 05 May 2021 23:21:43 +0000 In-Reply-To: <87tunjsfnm.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Mon, 03 May 2021 13:53:17 -0700") Received-SPF: pass client-ip=45.79.25.59; envelope-from=kfogel@red-bean.com; helo=sanpietro.red-bean.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:268942 Archived-At: On 03 May 2021, Eric Abrahamsen wrote: >I thought this was worth looking into more closely, and I'm >getting >closer to figuring out the problem. [...distant cheering from over the horizon...] >What we really need is to update the "active" number for the >receiving >group -- that's Gnus' final authoritative figure for how many >articles >are in the group, and if it's not updated then we see Karl's >situation >where you enter the receiving group and don't see the moved >articles, >until you do a full refresh of the group. > >The calls to `gnus-group-get-new-news-this-group' make the world >right >only because they end up calling >`gnus-get-unread-articles-in-group', >which updates the group's active number (in addition to a bunch >of other >stuff). > >What I'm trying to figure out now is, what's the minimum amount >of code >we can run that does this work, without running a whole bunch of >other >unwanted processes. We can't just set the group's active number >directly, because we need to check the cache and the agent, and >update >the *Group* buffer, etc., as part of that. So we'll need some >combination of the "larger" functions, invoked properly, but I >haven't >figured out yet exactly how that will work. > >But anyway, the mystery is clearing. Thank you so much for looking further into this. Your reasoning & questions above seem exactly right to me. Knowing this "combination of the 'larger' functions, invoked properly" would be a good thing, and I think might be of general utility in the Gnus code. Surely this isn't the only place where a group needs to be told that its article set has changed and that it needs to refresh itself in a local-only way. By the way, I received your message twice, with two separate Message-ID headers: Message-ID: <87v97zsfod.fsf@ericabrahamsen.net> Message-ID: <87tunjsfnm.fsf@ericabrahamsen.net> Letting you know just in case that's a manifestation of some kind of message-sending buglet. (Since I was an explicit recipient in the headers, along with emacs-devel, I wondered if maybe your MUA or MDA somehow generates a distinct message, with its own Message-ID, for each recipient, instead of all recipients getting the same message.) Best regards, -Karl