Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <jas@extundo.com>
Subject: Re: Gnus doesn't update nntp marks files when unplugged
Date: Tue, 18 Apr 2006 10:50:51 +0200	[thread overview]
Message-ID: <87hd4rtggk.fsf@latte.josefsson.org> (raw)
In-Reply-To: <m3zmir2i3w.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Wed, 12 Apr 2006 12:39:15 +0200")

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

> Katsumi Yamaoka <yamaoka@jpl.org> writes:
>
>> ;; I added Lars to Cc:.
>>
>> Does anyone know what is *exceedingly slow*?  I'm using only
>> nntp and nnml, moreover am always plugged, so it is hard to
>> imagine what kind of back end slows Gnus down by synchronizing
>> flags.
>>
>>>> 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.
>
> It was taking several minutes for me...  If there's still interest in
> this, I can switch it back on again and see how that goes.

Yes, please do.  Nnimap users are bitten by this behaviour when they
try the agent.  The result is that none of the flag changes made while
offline are synchronized back to the server if that flag is disabled.
I think the default should be t.  It has always been quite fast for
me.



  reply	other threads:[~2006-04-18  8:50 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
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 [this message]
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=87hd4rtggk.fsf@latte.josefsson.org \
    --to=jas@extundo.com \
    /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).