[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#18728: 24.0.50; gnus hangs while reading mail from imap server
From: |
Ted Zlatanov |
Subject: |
bug#18728: 24.0.50; gnus hangs while reading mail from imap server |
Date: |
Thu, 16 Oct 2014 09:22:13 -0400 |
User-agent: |
Gnus/5.130012 (Ma Gnus v0.12) Emacs/25.0.50 (darwin) |
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/