From: Kevin Greiner <kgreiner@xpediantsolutions.com>
Subject: Re: Variable binding depth exceeds max-specpdl-size
Date: Thu, 08 Jul 2004 10:47:27 -0400 [thread overview]
Message-ID: <uy8lur1xc.fsf@xpediantsolutions.com> (raw)
In-Reply-To: <87fz84dirv.fsf@dod.no>
Steinar Bang <sb@dod.no> writes:
>>>>>> Steinar Bang <sb@dod.no>:
>
>>>>>> Kevin Greiner <kgreiner@xpediantsolutions.com>:
>>> How are you at debugging lisp?
>
>> Not very accomplished.
> [snip!]
>> Where do I go from here? What do I look for?
>
> In lack of any better idea (it doesn't look much like the C/C++
> debuggers I'm used to), I've stepped through forms with `d'.
>
> But I still don't really know what I'm supposed to be looking for.
What we're trying to figure out is why the (gnus-get-function
gnus-command-method 'request-type) form in nnagent-request-type is
returning nnagent-request-type when it should be returning
nnimap-request-type.
I can give you some hints but, since this is largely driven by your
configuration, I can not actually test it for you.
* gnus-get-function will, if gnus-agent is set (which you indicated it
is), call gnus-agent-get-function.
* gnus-agent-get-function calls gnus-online to see if the current
method is online. If it is, gnus-agent-get-function will return the
method (in your case nnimap) otherwise it returns nnagent.
* gnus-online looks up the current method in gnus-opened-servers to
determine whether the method has any status other than offline.
That appears to be where you are having trouble.
Kevin
next prev parent reply other threads:[~2004-07-08 14:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-05 18:16 Steinar Bang
2004-07-05 22:29 ` Kevin Greiner
2004-07-06 16:16 ` Steinar Bang
2004-07-06 19:42 ` Steinar Bang
2004-07-08 14:47 ` Kevin Greiner [this message]
2004-10-01 20:59 ` Steinar Bang
2004-10-01 22:17 ` Steinar Bang
2004-10-01 22:38 ` Steinar Bang
2004-10-01 22:48 ` Steinar Bang
2004-10-02 5:50 ` Kevin Greiner
2004-10-02 6:50 ` Steinar Bang
2012-12-13 8:30 Rémi Letot
2012-12-14 0:08 ` Katsumi Yamaoka
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=uy8lur1xc.fsf@xpediantsolutions.com \
--to=kgreiner@xpediantsolutions.com \
/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).