From: Lars Ingebrigtsen <larsi@gnus.org>
Date: Thu, 12 Apr 2018 16:12:03 +0000 (+0200)
Subject: Ensure that non-QRESYNC nnimap can proceed after a QRESYNC fail
X-Git-Tag: emacs-27.0.90~5282
X-Git-Url: http://git.eshelyaron.com/gitweb/?a=commitdiff_plain;h=4616ddc1316f9e25429ab932bf87149dc578381d;p=emacs.git

Ensure that non-QRESYNC nnimap can proceed after a QRESYNC fail

* lisp/gnus/nnimap.el (nnimap-update-info): If we don't have a
start-article in the non-QRESYNC case, then the start has to be 1
(bug#23241).
---

diff --git a/lisp/gnus/nnimap.el b/lisp/gnus/nnimap.el
index ffe1a47e932..a884376efb6 100644
--- a/lisp/gnus/nnimap.el
+++ b/lisp/gnus/nnimap.el
@@ -1544,6 +1544,8 @@ If LIMIT, first try to limit the search to the N last articles."
 	       info existing (nnimap-imap-ranges-to-gnus-ranges vanished) flags)
 	    ;; Do normal non-QRESYNC flag updates.
 	    ;; Update the list of read articles.
+	    (unless start-article
+	      (setq start-article 1))
 	    (let* ((unread
 		    (gnus-compress-sequence
 		     (gnus-set-difference