[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: max-lisp-eval-depth
From: |
Perry Smith |
Subject: |
Re: max-lisp-eval-depth |
Date: |
Wed, 30 Jan 2013 14:00:02 -0600 |
Mine is set to 600 (emacs 24.2) on two different platforms.
Would setting debug-on-error to t help? Then you would see the stack and that
might give you a hint. It may be some data structure is looped back on itself
and its not suppose to be causing infinite recursion.
On Jan 30, 2013, at 1:42 PM, drain wrote:
> The following issue is raised when I use Wanderlust, but it must relate to
> Emacs at large, given that the variable max-lisp-eval-depth is defined in
> emacs/src/eval.c.
>
> Plus the Wanderlust mailing list is only semi-active.
>
> The issue:
>
> When I relaunch Wanderlust sometimes (within the same Emacs session), I get
> the message, "Lisp nesting exceeds max-eval-depth." Because of this,
> Wanderlust will not update my inbox. It shows what I had before.
>
> And then other times, I can't enter my Inbox because of
> "max-lisp-eval-depth."
>
> Maybe there's some variable here, perhaps max-lisp-eval-depth, I need to
> set to a different value.
>
> Now so that this does not appear like a case of
> answering my own question, I am asking what the ideal value should be,
> given the problem as described (I'm still just presuming that the value of
> that variable is the source of the problem; conjecturing to my own
> question, not answering it).
>
> My current solution is to completely kill all mail processes, then launch
> Wanderlust afresh.
>
>
>
> --
> View this message in context:
> http://emacs.1067599.n5.nabble.com/max-lisp-eval-depth-tp276835.html
> Sent from the Emacs - Help mailing list archive at Nabble.com.
>