unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Pankaj Jangid <pankaj@codeisgreat.org>
To: 56179@debbugs.gnu.org
Subject: bug#56179: 29.0.50; Gnus not opening imap group - wrong type argument, listp
Date: Fri, 24 Jun 2022 11:16:20 +0530	[thread overview]
Message-ID: <87fsjufwb7.fsf@codeisgreat.org> (raw)
In-Reply-To: <87zgi2lj74.fsf@codeisgreat.org> (Pankaj Jangid's message of "Fri, 24 Jun 2022 11:03:03 +0530")

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

attached small patch fixes the issue.


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-ranges-should-always-be-a-list.patch --]
[-- Type: text/x-diff, Size: 869 bytes --]

From 9bd0872326c7dd88eaa80476e669c075c91f3894 Mon Sep 17 00:00:00 2001
From: Pankaj Jangid <pankaj@codeisgreat.org>
Date: Fri, 24 Jun 2022 11:13:39 +0530
Subject: [PATCH] "ranges" should always be a list

---
 lisp/gnus/nnimap.el | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lisp/gnus/nnimap.el b/lisp/gnus/nnimap.el
index c158367b73..a69b5c7727 100644
--- a/lisp/gnus/nnimap.el
+++ b/lisp/gnus/nnimap.el
@@ -239,7 +239,7 @@ nnimap-retrieve-headers
     (when (nnimap-change-group group server)
       (with-current-buffer (nnimap-buffer)
 	(erase-buffer)
-        (let ((ranges (gnus-compress-sequence articles))
+        (let ((ranges (gnus-compress-sequence articles t))
               sequence)
           ;; If we have a lot of ranges, split them up to avoid
           ;; generating too-long lines.  (The limit is 8192 octects,
-- 
2.30.2


  reply	other threads:[~2022-06-24  5:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-24  3:16 bug#56179: 29.0.50; Gnus not opening imap group - wrong type argument, listp Pankaj Jangid
2022-06-24  5:33 ` Pankaj Jangid
2022-06-24  5:46   ` Pankaj Jangid [this message]
2022-06-24  9:24     ` Lars Ingebrigtsen
2022-06-24 11:15       ` Pankaj Jangid

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87fsjufwb7.fsf@codeisgreat.org \
    --to=pankaj@codeisgreat.org \
    --cc=56179@debbugs.gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).