From: Perry Smith <pedzsan@gmail.com>
To: drain <aeuster@gmail.com>
Cc: Help-gnu-emacs@gnu.org
Subject: Re: max-lisp-eval-depth
Date: Wed, 30 Jan 2013 14:00:02 -0600 [thread overview]
Message-ID: <6DCBB657-5C42-4655-A9E4-AFCF4CC3853B@gmail.com> (raw)
In-Reply-To: <1359574923315-276835.post@n5.nabble.com>
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.
>
next prev parent reply other threads:[~2013-01-30 20:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-30 19:42 max-lisp-eval-depth drain
2013-01-30 20:00 ` Perry Smith [this message]
2013-01-30 21:27 ` max-lisp-eval-depth Drew Adams
2013-01-30 22:00 ` max-lisp-eval-depth drain
[not found] <mailman.18654.1359574929.855.help-gnu-emacs@gnu.org>
2013-01-30 22:01 ` max-lisp-eval-depth Stefan Monnier
2013-01-31 3:08 ` max-lisp-eval-depth drain
[not found] ` <mailman.18689.1359601697.855.help-gnu-emacs@gnu.org>
2013-01-31 14:54 ` max-lisp-eval-depth jack-mac
2013-01-31 15:04 ` max-lisp-eval-depth Ludwig, Mark
2013-01-31 17:33 ` max-lisp-eval-depth drain
2013-01-31 18:28 ` max-lisp-eval-depth Oleksandr Gavenko
2013-02-01 20:46 ` max-lisp-eval-depth Stefan Monnier
2013-02-02 19:25 ` max-lisp-eval-depth drain
2013-02-02 19:27 ` max-lisp-eval-depth Drew Adams
2013-02-03 4:53 ` max-lisp-eval-depth drain
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=6DCBB657-5C42-4655-A9E4-AFCF4CC3853B@gmail.com \
--to=pedzsan@gmail.com \
--cc=Help-gnu-emacs@gnu.org \
--cc=aeuster@gmail.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.