From: Dave Goldberg <david.goldberg6@verizon.net>
To: ding@gnus.org
Subject: Re: Problems with new imap-fetch-safe in XEmacs 21.4.21
Date: Wed, 07 Jan 2009 10:15:33 -0500 [thread overview]
Message-ID: <848wpnywoa.fsf@incoming.verizon.net> (raw)
In-Reply-To: <b4meizfo5cz.fsf@jpl.org> (Katsumi Yamaoka's message of "Wed, 07 Jan 2009 18:03:24 +0900")
>>>>> On Wed, 07 Jan 2009 18:03:24 +0900, Katsumi Yamaoka <yamaoka@jpl.org> #kKnN,xUnmKia.'[pp`;Omh}odZK)?7wQSl"4o04=EixTF+V[""w~iNbM9ZL+.b*_CxUmFk B#Fu[*?MZZH@IkN:!"\w%I_zt>[$nm7nQosZ<3eu;B:$Q_:p!',P.c0-_Cy[dz4oIpw0ESA^D*1Lw= L&i*6&( said:
>>>>> 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:
[...]
The patch solved the problem for me. Thanks!
--
Dave Goldberg
david.goldberg6@verizon.net
prev parent reply other threads:[~2009-01-07 15:15 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
2009-01-07 15:15 ` Dave Goldberg [this message]
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=848wpnywoa.fsf@incoming.verizon.net \
--to=david.goldberg6@verizon.net \
--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).