Gnus development mailing list
 help / color / mirror / Atom feed
From: David Engster <deng@randomsample.de>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Giorgos Keramidas <keramida@ceid.upatras.gr>,
	Katsumi Yamaoka <yamaoka@jpl.org>,
	ding@gnus.org, emacs-devel@gnu.org
Subject: Re: Emacs trunk and Gnus master are fully sync'd now
Date: Sat, 06 Jul 2013 17:44:30 +0200	[thread overview]
Message-ID: <87ppuv4rs1.fsf@randomsample.de> (raw)
In-Reply-To: <87a9lz1zpj.fsf@building.gnus.org> (Lars Ingebrigtsen's message of "Sat, 06 Jul 2013 17:21:28 +0200")

Lars Ingebrigtsen writes:
> keramida@ceid.upatras.gr (Giorgos Keramidas) writes:
>
>> The next time I start Gnus it tries to do an 'initial sync of 129
>> groups' all over again, and this delays startup time a lot.
>
> Yes, this is the bug that has made me want to not merge that bit of Ma
> Gnus into bzr Emacs.  I still have no fix for it.

I cannot reproduce this anymore in Dovecot after my change which keeps
empty 'unexist' ranges. So the question is why it still happens with
GMail.

@Giorgos: Does it only happen on startup or also sometimes when you
press 'g'?

AFAICS in `nnimap-retrieve-group-data-early', the resync should only
happen when there's either no 'active', 'unexist', or
'uidvalidity'. Perhaps the first step should be to install some verbose
messaging which says which of those triggers the resync.

-David



  reply	other threads:[~2013-07-06 15:44 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-02 10:40 Katsumi Yamaoka
2013-07-02 16:52 ` Giorgos Keramidas
2013-07-06 15:21   ` Lars Ingebrigtsen
2013-07-06 15:44     ` David Engster [this message]
2013-07-06 18:45       ` David Engster
2013-07-06 20:03         ` David Engster
2013-07-07 13:27           ` Giorgos Keramidas
2013-07-07 13:24       ` Giorgos Keramidas
2013-07-07 19:51         ` David Engster
2013-07-08 13:16           ` Giorgos Keramidas
2013-07-08 18:24             ` David Engster
2013-07-09 11:08               ` Giorgos Keramidas
2013-07-09 15:34                 ` David Engster
2013-07-09 18:16                   ` Giorgos Keramidas
2013-07-09 19:33                     ` David Engster
2013-07-09 19:39                       ` Ted Zlatanov
2013-07-09 20:41                       ` Giorgos Keramidas
2013-07-09 21:42                         ` David Engster
2013-07-10 15:32                           ` Ted Zlatanov
2013-07-10 19:17                           ` David Engster
2013-07-11 17:12                             ` Giorgos Keramidas
2013-07-18 13:31                           ` Lars Magne Ingebrigtsen
2013-07-18 15:42                             ` Giorgos Keramidas
2013-07-18 16:55                               ` David Engster
2013-07-18 17:15                                 ` Giorgos Keramidas
2013-07-30 14:56                               ` Lars Magne Ingebrigtsen
2013-07-30 19:58                                 ` Giorgos Keramidas

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=87ppuv4rs1.fsf@randomsample.de \
    --to=deng@randomsample.de \
    --cc=ding@gnus.org \
    --cc=emacs-devel@gnu.org \
    --cc=keramida@ceid.upatras.gr \
    --cc=larsi@gnus.org \
    --cc=yamaoka@jpl.org \
    /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).