From: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: ksinya@quartz.ocn.ne.jp
Subject: Re: Gnus doesn't update nntp marks files when unplugged
Date: Wed, 01 Feb 2006 13:51:06 +0900 [thread overview]
Message-ID: <b4m7j8flm11.fsf@jpl.org> (raw)
In-Reply-To: <b4mzmlc7fho.fsf@jpl.org>
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.
next prev parent reply other threads:[~2006-02-01 4:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-31 12:23 Katsumi Yamaoka
2006-02-01 4:51 ` Katsumi Yamaoka [this message]
2006-02-01 12:46 ` Simon Josefsson
2006-02-02 9:33 ` Katsumi Yamaoka
2006-04-12 10:39 ` Lars Magne Ingebrigtsen
2006-04-18 8:50 ` Simon Josefsson
2006-04-18 16:27 ` Lars Magne Ingebrigtsen
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=b4m7j8flm11.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=ksinya@quartz.ocn.ne.jp \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).