Re: Gnus doesn't update nntp marks files when unplugged

[Simon Josefsson <jas@extundo.com>]

Katsumi Yamaoka <yamaoka@jpl.org> writes:

> Oops, this is probably a FAQ.
>
>>>>>> In <b4mzmlc7fho.fsf@jpl.org> Katsumi Yamaoka wrote:
>
>> .marks files for nntp groups aren't updated when Gnus is
>> unplugged.
>
> I realized people who use the nntp marks feature on purpose and
> usually read articles in the unplugged condition should set the
> gnus-agent-synchronize-flags variable to non-nil.
>
> 2005-09-20  Lars Magne Ingebrigtsen  <larsi@gnus.org>
>
> 	* gnus-agent.el (gnus-agent-synchronize-flags): Switch the
> 	default to nil, to be able to use Gnus at all.  If the default
> 	switches to something else, then the function should be fixed not
> 	be exceedingly slow.
>
> 2004-07-09  Simon Josefsson  <jas@extundo.com>
>
> 	* gnus-agent.el (gnus-agent-synchronize-flags): Revert to ask.
> 	Users will lose all flag changes made while unplugged with
> 	e.g. nntp unless flag synchronization happens, thus `nil' is not a
> 	good default.  See numerous reports on ding mailing list.
>
> IMHO, we should set gnus-agent-synchronize-flags to t by default
> or synchronize at least nntp marks automatically when Gnus is
> re-plugged even if it takes time.  I don't know how it is slow
> so far, though.

I agree.  I have never found it that slow.  It is not disk or network
bound.  I read pretty large nntp groups offline, and syncing the flags
doesn't seem to take that long.