Gnus development mailing list
 help / color / mirror / Atom feed
From: Vincent Bernat <bernat@luffy.cx>
To: ding@gnus.org
Subject: Re: Unable to get all messages in an IMAP group
Date: Wed, 04 Feb 2015 22:11:03 +0100	[thread overview]
Message-ID: <m3d25p757c.fsf@neo.luffy.cx> (raw)
In-Reply-To: <m3h9v17690.fsf@neo.luffy.cx> (Vincent Bernat's message of "Wed, 04 Feb 2015 21:48:27 +0100")

[-- Attachment #1: Type: text/plain, Size: 632 bytes --]

 ❦  4 février 2015 21:48 +0100, Vincent Bernat <bernat@luffy.cx> :

>> Ah, the speedup-on-large-imap-move commit, I think...?
>>  http://thread.gmane.org/gmane.emacs.gnus.general/85440
>
> Yes.
>
> Unfortunately, in my case, this is not fixed in today master. Before the
> patch, M-g does:
>
> #v+
> 21:46:17 [] 106 SELECT "INBOX"
> 21:46:17 [] 107 UID FETCH 1:* FLAGS
> #v-
>
>
> After the patch, it does:
>
> #v+
> 21:44:23 [] 9626 EXAMINE "INBOX" (QRESYNC (1402209543 15465))
> #v-
>
> What easy way do I have to restore M-g behaviour to issue a full
> refresh?

I am fixing that with this patch:


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-nnimap-fix-group-scan-request.patch --]
[-- Type: text/x-diff, Size: 1506 bytes --]

From 025abeeebac0c196b8efa3aa538bcc69b7037374 Mon Sep 17 00:00:00 2001
From: Vincent Bernat <vincent@bernat.im>
Date: Wed, 4 Feb 2015 22:08:48 +0100
Subject: [PATCH] nnimap: fix group scan request

`gnus-group-get-new-news-this-group' was not refreshing the group with
the newly introduced `nnimap-request-group-scan' method due to two
naming problems.
---
 lisp/gnus-int.el | 2 +-
 lisp/nnimap.el   | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/lisp/gnus-int.el b/lisp/gnus-int.el
index dd938ce07586..4e870bb84bb9 100644
--- a/lisp/gnus-int.el
+++ b/lisp/gnus-int.el
@@ -442,7 +442,7 @@ If it is down, start it up (again)."
 (defun gnus-request-group-scan (group info)
   "Request that GROUP get a complete rescan."
   (let ((gnus-command-method (gnus-find-method-for-group group))
-	(func 'request-group-description))
+	(func 'request-group-scan))
     (when (gnus-check-backend-function func group)
       (funcall (gnus-get-function gnus-command-method func)
 	       (gnus-group-real-name group) (nth 1 gnus-command-method) info))))
diff --git a/lisp/nnimap.el b/lisp/nnimap.el
index e619c0f13c29..cdbc2a68709b 100644
--- a/lisp/nnimap.el
+++ b/lisp/nnimap.el
@@ -820,7 +820,7 @@ textual parts.")
 			group))
 	t))))
 
-(deffoo nnimap-request-scan-group (group &optional server info)
+(deffoo nnimap-request-group-scan (group &optional server info)
   (setq group (nnimap-decode-gnus-group group))
   (let (marks high low)
     (with-current-buffer (nnimap-buffer)
-- 
2.1.4


[-- Attachment #3: Type: text/plain, Size: 102 bytes --]


-- 
It is a wise father that knows his own child.
		-- William Shakespeare, "The Merchant of Venice"

  parent reply	other threads:[~2015-02-04 21:11 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-02 23:18 Vincent Bernat
2015-02-03  6:42 ` Steinar Bang
2015-02-03  7:40   ` Vincent Bernat
2015-02-03  7:44     ` Vincent Bernat
2015-02-03  8:05     ` Steinar Bang
2015-02-03  8:17       ` Tassilo Horn
2015-02-03  9:09       ` Vincent Bernat
2015-02-03 10:54         ` Steinar Bang
2015-02-03 20:52           ` Vincent Bernat
2015-02-04  6:28             ` Steinar Bang
2015-02-04 20:48               ` Vincent Bernat
2015-02-04 21:10                 ` Steinar Bang
2015-02-04 21:11                 ` Vincent Bernat [this message]
2015-02-04 21:19                   ` Vincent Bernat
2015-02-04 21:35                     ` Vincent Bernat
2015-02-05  3:10                       ` Lars Ingebrigtsen
2015-02-05  6:27                         ` Vincent Bernat
2015-02-05  3:06                   ` Lars Ingebrigtsen

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=m3d25p757c.fsf@neo.luffy.cx \
    --to=bernat@luffy.cx \
    --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).