From: "Drew Adams" <drew.adams@oracle.com>
To: "'Perry Smith'" <pedzsan@gmail.com>, "'drain'" <aeuster@gmail.com>
Cc: Help-gnu-emacs@gnu.org
Subject: RE: max-lisp-eval-depth
Date: Wed, 30 Jan 2013 13:27:42 -0800 [thread overview]
Message-ID: <2648A59CF1C84AF884198413B12B188D@us.oracle.com> (raw)
In-Reply-To: <6DCBB657-5C42-4655-A9E4-AFCF4CC3853B@gmail.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.
The error that max-lisp-eval-depth is exceeded is nearly always an
infinite-recursion problem. Bisect your init file to try to identify the
culprit code.
You might need to recompile that code or load it without compiling it. Or
perhaps (most likely) it is just buggy and needs to be fixed.
But the point is to respond to a max-lisp-eval-depth error by looking for a code
problem, not by increasing that variable value.
next prev parent reply other threads:[~2013-01-30 21:27 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 ` max-lisp-eval-depth Perry Smith
2013-01-30 21:27 ` Drew Adams [this message]
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=2648A59CF1C84AF884198413B12B188D@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=Help-gnu-emacs@gnu.org \
--cc=aeuster@gmail.com \
--cc=pedzsan@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.