From: Nevin Kapur <nevin@jhu.edu>
Subject: Re: nnimap hanging when checking mail
Date: Fri, 06 Dec 2002 08:32:34 -0500 [thread overview]
Message-ID: <m3adjjl1cd.fsf@fermat.mts.jhu.edu> (raw)
In-Reply-To: <ilur8cwcbfh.fsf@extundo.com>
Simon Josefsson <jas@extundo.com> writes:
> "Nevin Kapur" <nevin@jhu.edu> writes:
>
>> Yesterday I moved a rather large hierarchy under IMAP control and every
>> since then 5 times out 6, when nnimap checks mail, it makes the
>> connection, then says
>>
>> nnimap: Checking mailboxes...
>>
>> and then just hangs.
> I think reporting it to the XEmacs people, like you did, is the best
> way. It is difficult to debug or solve non-elisp problems in elisp.
> Meanwhile, maybe trying Emacs is a workaround. Frobbing `imap-log'
> and looking in *imap-log* might give hints if you want to edebug
> {nni,}imap.el further.
Thanks for the advice. The problem with debugging is that when XEmacs
hangs, there is nothing more I can seemingly do. I don't know how to
recover the information in *imap-log* after XEmacs has hung.
Hopefully some XEmacs developer will have some ideas...
-Nevin
prev parent reply other threads:[~2002-12-06 13:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-05 20:06 Nevin Kapur
2002-12-05 23:07 ` Simon Josefsson
2002-12-06 13:32 ` 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=m3adjjl1cd.fsf@fermat.mts.jhu.edu \
--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).