From: Nevin Kapur <nevin@jhu.edu>
Subject: Re: Error trying to browse an imap server
Date: Fri, 28 Sep 2001 08:06:57 -0400 [thread overview]
Message-ID: <m3ofnv8qou.fsf@bombay.dyndns.org> (raw)
In-Reply-To: <Pine.LNX.4.33.0109281021360.26785-100000@lie.extundo.com> (Simon Josefsson's message of "Fri, 28 Sep 2001 10:22:06 +0200 (CEST)")
Simon Josefsson <jas@extundo.com> writes:
> On Thu, 27 Sep 2001, Nevin Kapur wrote:
>
>> In the *Server* buffer when I try to browse my IMAP server, I get the
>> following backtrace:
>>
>> Signaling: (wrong-type-argument sequencep quote)
>> concat("LIST \"" nil "\" \"" quote nil "%\"")
>
> Do you use `nnimap-list-pattern'? What is the contents of it?
(quote ("INBOX" "mail/*" "Sent Items" "Draft" "Trash"))
Ah...I see my error. I changed it to
("INBOX" "mail/*" "Sent Items" "Draft" "Trash*")
and the error went away.
Sorry about the noise.
--
Nevin Kapur
nevin@jhu.edu
prev parent reply other threads:[~2001-09-28 12:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-28 3:15 Nevin Kapur
2001-09-28 8:22 ` Simon Josefsson
2001-09-28 12:06 ` Nevin Kapur [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=m3ofnv8qou.fsf@bombay.dyndns.org \
--to=nevin@jhu.edu \
/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).