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: Sun, 11 Apr 2021 01:02:44 -0500 Message-ID: <87fszx1hq3.fsf@red-bean.com> References: <87lf9rruzl.fsf@red-bean.com> <87mtu65yqj.fsf@igel.home> <87mtu5iyv8.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="30085"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: Andreas Schwab , Stefan Monnier , Emacs Development To: Eric Abrahamsen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Apr 11 08:03:41 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 1lVTC9-0007j0-2u for ged-emacs-devel@m.gmane-mx.org; Sun, 11 Apr 2021 08:03:41 +0200 Original-Received: from localhost ([::1]:55656 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lVTC8-0001XA-3M for ged-emacs-devel@m.gmane-mx.org; Sun, 11 Apr 2021 02:03:40 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:55302) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lVTBM-00014t-9l for emacs-devel@gnu.org; Sun, 11 Apr 2021 02:02:53 -0400 Original-Received: from sanpietro.red-bean.com ([45.79.25.59]:54248) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lVTBI-0002vO-9Q for emacs-devel@gnu.org; Sun, 11 Apr 2021 02:02:51 -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=+O5c7Epa3Xk3WcwU0Q6pQUZk7dsQn1GrQds/EMp/wqo=; t=1618120967; x=1619330567; b=BZ9UgpHBo6dyB/yBNlGOEEHHxKhckq3VuXNN/YwW1X87KVuLFxzbR9go6QwcEONjvsp8hd+M6M eCD3fBGGHWjzAGAzyMEaS8yqTwNhaqNlXwyMAmz9IHET7wdWiun/E87RxrG6GTWqCrtn281oKnNuP som+9F75qUSxMp2zXDuD71y3uKZu5lVVrZyNXB71gnn9R2dRZ2dDxunqS4txNXX/NJb/9Du8yhud3 2QGfWvHLq4xF07i/iua4OzgEP7uHVrmo6YK9FVkGsJtqEqn/0YoE8HYuxZL3VFsfotAbH6PvBuSlo 0l5RQgHLjy5uXz2wAeWCJor0Tyr5LHiQYVSxQ==; Original-Received: from 99-112-125-163.lightspeed.cicril.sbcglobal.net ([99.112.125.163]:46918 helo=floss) by sanpietro.red-bean.com with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lVTBF-0004MW-Td; Sun, 11 Apr 2021 06:02:46 +0000 In-Reply-To: <87mtu5iyv8.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Sat, 10 Apr 2021 15:00:27 -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:267852 Archived-At: On 10 Apr 2021, Eric Abrahamsen wrote: > Stefan Monnier writes: > >>>> I expected article-moving to be an entirely local operation, >>>> and to have nothing to do with fetching new news. After all, >>>> Gnus already has the article in question -- it's not "new". >>> What if the destination group has been updated in the mean >>> time? Gnus needs to know the current status of the group, >>> before it can write to it. >> >> But what if it gets updated *again* before we actually write to >> it? > > Also, in this case, it's updated *after* the article is moved to > it. Yeah, that's the thing that puzzles me. By this point, the article has already been moved to the destination group. There can't be (I think?) any justification for fetching new news to the destination group right then. The user certainly hasn't asked for that to happen. (Sorry for the strange formatting in my original couple of posts, by the way. I was experimenting with `use-hard-newlines' in Message Mode, but I now see how that doesn't quite do the right thing in prose messages that contain code-like blocks interleaved with the regular paragraphs. I've started using the helpful `messages-are-flowing' package while I ponder how best to solve this.) Best regards, -Karl