Re: updating backend marks immediately

[Dan Christensen <jdc@uwo.ca>]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

>>> Yes.  I've now made it clear the marks before moving.
>
> It occurs to me that I should probably have do it the other way around.
> That is, set the marks on the article before moving it, and then not
> bother to copy over the marks afterwards.  The result should be much the
> same, but slightly more secure if something fails in the middle.

I think what you propose might be better.  What I see now is that
when I move a message from my INBOX to another folder (a common
operation), my mail-notification daemon pops up a notification saying
that there's a new message in my INBOX.  That's because Gnus briefly
removes the marks.  Instead, Gnus should just upload any pending changes
to the marks (and only if there are any changes to save), and then move
the article.

This should also be faster, since now there are several round-trips, 
even if the marks don't need to be updated:  1) clear the marks,
2) do the move, 3) fix the marks in the target group (and some other
actions that I'm omitting, like looking up the article number).
In many cases, 1 and 3 can be skipped, and when the marks do need
to be adjusted, it should still be doable in two steps, not three.

Dan