Gnus development mailing list
 help / color / mirror / Atom feed
From: Steinar Bang <sb@dod.no>
To: ding@gnus.org
Subject: Re: Unable to select group (nnimap) but gnus can split from it
Date: Thu, 15 Nov 2012 14:49:05 +0100	[thread overview]
Message-ID: <yb0boez563y.fsf@dod.no> (raw)
In-Reply-To: <86zk2jlvg1.fsf@freeenv.ad.medctr.ucla.edu>

>>>>> Aric Gregson <aorchid@mac.com>:
> Steinar Bang <sb@dod.no> writes:

>> The new nnimap is a lot faster than the previous version because it uses
>> QRESYNC to find new messages.  To be able to do so, it needs to store
>> the state of the group in nnimap.eld as well.  `M-g' does a full sync
>> and updates the .newsrc.eld so that QRESYNC will do the right thing.

> It seems like it does, but I have to do it repeatedly.

Right.  If I'm to guess, this is because a full sync works, but QRESYNC
doesn't.

As for why QRESYNC doesn't work, I don't know.  It could be because the
server in question doesn't support it, or it could be something wrong
with the request or the response (it can be something as little as a SPC
too many or to little, as a different IMAP server proved).

Anyway, a workaround here could be to fall back to making `g' do full
sync of nnimap groups to find new messages.  But I don't know if this is
possible to do with the new nnimap...?


Of course, full sync is slooo-oo-o-w, which is why the new nnimap
uses, or tries to use, QRESYNC...





  reply	other threads:[~2012-11-15 13:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-08 20:26 Aric Gregson
2012-11-09  1:12 ` Eric Fraga
2012-11-09  1:43   ` Aric Gregson
2012-11-11  9:53     ` lee
2012-11-09  2:02   ` Aric Gregson
2012-11-09 23:03     ` Steinar Bang
2012-11-10  0:13       ` Aric Gregson
2012-11-10  7:37         ` Steinar Bang
2012-11-14 21:35           ` Aric Gregson
2012-11-15 13:49             ` Steinar Bang [this message]
2012-11-17 18:01               ` Aric Gregson

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=yb0boez563y.fsf@dod.no \
    --to=sb@dod.no \
    --cc=ding@gnus.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).