Re: Old news keeps coming back.

[raphael.berbain@free.fr (Raphaël Berbain)]

Barry Fishman <barry_fishman@att.net> writes:

> Simon Josefsson <jas@extundo.com> writes:
>
>> Barry Fishman <barry_fishman@att.net> writes:
>>
>>> Using the CVS version of GNUS I find that when I read news offline,
>>> exit news (normally) and come back later, read new news, and go
>>> offline, I find the messages I have read are listed again as if they
>>> were not seen.

FWIW, I see the same thing here.  Quite reproductible, too:  Read
some group, quit Gnus, start Gnus again, go online, get new news.
Old articles appear as unread/seen.

>> Maybe you need to synchronize the marks changes when going online, now
>> that nntp uses marks.
>>
>> What's the value of gnus-agent-synchronize-flags?
>>
>> I notice that the default value for that variable has changed
>> recently, but I missed the discussion on that, can someone provide a
>> pointer?
>
> My gnus-agent-synchronize-flags value has its default value of nil.
> Should I suppose that I need to set this to true.

Setting it to t solved the issue for me.  However, the documentation
is misleading/out of sync:  It says the default value for g-a-s-f is
'ask, whereas it is now nil.  Also, it appears in the Agent and IMAP
node, while it now seems relevant to nntp as well.

All in all, it seems to me that the default setup is broken:  With
g-a-s-f set to t and agentized nntp, old articles come back.  Maybe
it is dependant on some other bit of config, though.

So the questions: Does anybody know why Lars changed the default
g-a-s-f value to nil ?  What is this nntp marks stuff anyway ?  Marks
w/ imap, I get it, but I basically can't write anything on the nntp
servers I use.  Why does Gnus even try to synchronize marks with
nntp ?