From: David Engster <deng@randomsample.de>
To: ding@gnus.org
Subject: What happened to snappy low-bandwidth nnimap?
Date: Tue, 07 Aug 2012 20:47:06 +0200 [thread overview]
Message-ID: <87sjby8rpx.fsf@randomsample.de> (raw)
I'm currently on vacation with no 3G and terrible reception to
boot. We're talking roughly 2kb/s, so it's totally, like, 1992 or so.
Gnus' nnimap used to be pretty snappy with low bandwidths, but now I get
"Initial sync of 2 groups (please wait)" and it downloads about 700kb of
data. While that in itself is pretty bad, I could probably live with it
if it actually did this once, but it does it almost *every* time; so
much for "initial".
So my most pressing question is: how do I turn that off? I guess it's
some new feature for fixing that long standing "wrong unread count"
thingy, but please, I need my snappy Gnus back.
-David
next reply other threads:[~2012-08-07 18:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-07 18:47 David Engster [this message]
2012-08-08 15:41 ` Richard Riley
2012-08-08 18:46 ` Steinar Bang
2012-08-08 20:00 ` David Engster
2012-08-08 20:21 ` Michael Welsh Duggan
2012-08-08 20:36 ` David Engster
2012-08-09 20:26 ` David Engster
2012-09-04 22:09 ` Lars Ingebrigtsen
2012-08-08 20:03 ` Dave Abrahams
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=87sjby8rpx.fsf@randomsample.de \
--to=deng@randomsample.de \
--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).