Gnus development mailing list
 help / color / mirror / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: Problems with new imap-fetch-safe in XEmacs 21.4.21
Date: Wed, 07 Jan 2009 18:03:24 +0900	[thread overview]
Message-ID: <b4meizfo5cz.fsf@jpl.org> (raw)
In-Reply-To: <84k598fki0.fsf@incoming.verizon.net>

>>>>> Dave Goldberg wrote:
> I get the following on GCC to an Exchange 2007 mailbox now.  The GCC
> actually does succeed but the error is annoying nonetheless.  Lisp backtrace:

> Debugger entered--Lisp error: (wrong-type-argument numberp "*:*")
>   signal(wrong-type-argument (numberp "*:*"))
>   byte-code("..." [receive props uids buffer imap-enable-exchange-bug-workaround data string-match "The specified message set is invalid" make-local-variable t imap-fetch signal nouidfetch] 5)
>   imap-fetch-safe(("*" "*:*") "UID")
>   imap-message-appenduid-1("Sent Items")

[...]

The first argument passed to `imap-fetch-safe' seems to have to
be a cons, not a list.  If that is a list, it is passed to
`number-to-string' by way of `imap-list-to-message-set' and
causes the `wrong-type-argument' error.  This is no more than a
guess since I don't use IMAP, but here is a patch:

--8<---------------cut here---------------start------------->8---
--- imap.el~	2009-01-04 21:39:51 +0000
+++ imap.el	2009-01-07 09:02:11 +0000
@@ -1870,7 +1870,7 @@
 	  (imap-message-data (make-vector 2 0)))
       (when (imap-mailbox-examine-1 mailbox)
 	(prog1
-	    (and (imap-fetch-safe '("*" "*:*") "UID")
+	    (and (imap-fetch-safe '("*" . "*:*") "UID")
 		 (list (imap-mailbox-get-1 'uidvalidity mailbox)
 		       (apply 'max (imap-message-map
 				    (lambda (uid prop) uid) 'UID))))
--8<---------------cut here---------------end--------------->8---



  reply	other threads:[~2009-01-07  9:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-06 16:48 Dave Goldberg
2009-01-07  9:03 ` Katsumi Yamaoka [this message]
2009-01-07 15:15   ` Dave Goldberg

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=b4meizfo5cz.fsf@jpl.org \
    --to=yamaoka@jpl.org \
    --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).