Re: updating backend marks immediately

[Dan Christensen <jdc@uwo.ca>]

Ted Zlatanov <tzz@lifelogs.com> writes:

> I can't imagine why someone would want it just for a few
> servers or groups. 

Well, I don't see much point with local mail or nntp, since what I
did only propagates the mark changes to the remote server, but doesn't
update the .newsrc.  What does gnus-summary-update-info do for backends
besides nnimap?

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

> Ted Zlatanov <tzz@lifelogs.com> writes:
>
>> DC> (add-hook 'gnus-summary-update-hook 'gnus-summary-update-info)
>
>> I think it's worth a global variable.  gnus-update-marks-immediately or
>> something.
>
> I think the hook thing is a perfectly good solution here.

I don't mind either way.  But I should say that I've been noticing some
strange behavior with the above hook installed.  

First, I think there's a bug that was introduced when nnimap moves
within the same server were sped up a few weeks ago: if I have changed
the marks on an article, but not saved the summary, then after the move,
the article has its old marks.  This used to happen a long time ago,
then it was fixed a few months ago, and then it was broken again
recently.  (The above hook mostly hides this problem, but such moves
should be made to work for people not using the hook.)

The other bug/problem is harder to reproduce, and has occurred only
since adding the above hook.  Sometimes in an auto-expire group, I 
mark an article as unread (`u') or as read (`d') to get rid of the
expirable mark.  If I move the article, it sometimes retains the
expirable mark, even though marks should be propagated to the server.
Or, if I do `M-g' to regenerate the summary, sometimes the article
retains the expirable mark.  But I can't consistently reproduce this.

Finally, there's another problem, but I don't know if it's related to
the above hook.  I'm sometimes finding that gnus loses all expirable
marks on all articles, in both nnimap and nnfolder groups.  Again, I
can't figure out when this happens.  It might be related to using
`M-g' or `/ N' or such things.  Sorry I can't pin this down further.

I'm using git gnus from Nov 6:  commit 9f19eacda...

Dan