From: Ted Zlatanov <tzz@lifelogs.com>
To: tsugutomo.enami@jp.sony.com
Cc: 18728@debbugs.gnu.org
Subject: bug#18728: 24.0.50; gnus hangs while reading mail from imap server
Date: Thu, 16 Oct 2014 09:22:13 -0400 [thread overview]
Message-ID: <m238aokv3u.fsf@lifelogs.com> (raw)
In-Reply-To: <tkrtx36fegb.fsf@sigxcpu.sm.sony.co.jp> (tsugutomo enami's message of "Wed, 15 Oct 2014 07:56:20 +0900")
On Wed, 15 Oct 2014 07:56:20 +0900 tsugutomo.enami@jp.sony.com wrote:
te> The gnus hangs while reading mail from imap server on startup, with
te> displaying "nnimap read NNNNNNk" in mini buffer. The amount of NNNNNN
te> was about 200Mbytes.
...
te> The work around for me was adding code to ignore above NOOP lines in
te> nnimap-wait-for-response, as follows:
te> --- nnimap.el.orig 2011-06-01 09:27:58.000000000 +0900
te> +++ nnimap.el 2014-10-14 13:56:31.000000000 +0900
te> @@ -1683,7 +1689,8 @@
te> (while (and (not (bobp))
te> (progn
te> (forward-line -1)
te> - (looking-at "\\*"))))
te> + (or (looking-at "\\*")
te> + (looking-at "[0-9]+ OK NOOP")))))
te> (not (looking-at (format "%d .*\n" sequence)))))
te> (when messagep
te> (nnheader-message 7 "nnimap read %dk" (/ (buffer-size) 1000)))
te> I guess the NOOP lines are response for the NOOP command sent to keep a
te> connection. The gnus version used here is rather old but, at a glance,
te> the function in upstream repository is almost same.
Could you prepare a patch against Emacs trunk or (preferably) Gnus
master[1], incorporating Andreas' suggestion and with a ChangeLog entry?
I'll apply it to Gnus master and it will make its way to Emacs trunk
shortly thereafter.
Thanks
Ted
[1] http://git.gnus.org/
next prev parent reply other threads:[~2014-10-16 13:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-14 22:56 bug#18728: 24.0.50; gnus hangs while reading mail from imap server tsugutomo.enami
2014-10-15 7:59 ` Andreas Schwab
2014-10-16 13:22 ` Ted Zlatanov [this message]
2014-10-24 4:24 ` tsugutomo.enami
2014-10-24 6:06 ` Katsumi Yamaoka
2014-10-24 13:43 ` Ted Zlatanov
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=m238aokv3u.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=18728@debbugs.gnu.org \
--cc=tsugutomo.enami@jp.sony.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.