From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Karl Fogel <kfogel@red-bean.com>,
Andreas Schwab <schwab@linux-m68k.org>,
Emacs Development <emacs-devel@gnu.org>
Subject: Re: Why does Gnus article-moving act like a fetch of new news?
Date: Sat, 10 Apr 2021 15:00:27 -0700 [thread overview]
Message-ID: <87mtu5iyv8.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <jwvtuoewaqy.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Sat, 10 Apr 2021 09:06:07 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> 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.
next prev parent reply other threads:[~2021-04-10 22:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-09 21:47 Why does Gnus article-moving act like a fetch of new news? Karl Fogel
2021-04-10 4:11 ` Eric Abrahamsen
2021-04-10 4:58 ` Karl Fogel
2021-04-10 5:29 ` Eric Abrahamsen
2021-04-10 8:29 ` Andreas Schwab
2021-04-10 13:06 ` Stefan Monnier
2021-04-10 22:00 ` Eric Abrahamsen [this message]
2021-04-11 6:02 ` Karl Fogel
2021-04-11 16:05 ` Lars Ingebrigtsen
2021-04-12 17:05 ` Eric Abrahamsen
2021-04-12 17:56 ` Karl Fogel
2021-04-12 18:26 ` Eric Abrahamsen
2021-04-13 20:25 ` Karl Fogel
2021-04-13 21:59 ` Eric Abrahamsen
2021-04-14 3:27 ` Karl Fogel
2021-04-25 17:37 ` Lars Ingebrigtsen
2021-05-03 20:52 ` Eric Abrahamsen
2021-05-03 20:53 ` Eric Abrahamsen
2021-05-05 23:21 ` Karl Fogel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mtu5iyv8.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=emacs-devel@gnu.org \
--cc=kfogel@red-bean.com \
--cc=monnier@iro.umontreal.ca \
--cc=schwab@linux-m68k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.