From: Hongyi Zhao <hongyi.zhao@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: [External] : `max-specpdl-size' and `max-lisp-eval-depth'
Date: Sun, 26 Sep 2021 15:09:33 +0800 [thread overview]
Message-ID: <CAGP6POLwPP49y+EyDghDwrGFy5Skpp8pUdhkYfxxBa5wn1+Pyw@mail.gmail.com> (raw)
In-Reply-To: <SJ0PR10MB548832048983D53CE693B511F3A69@SJ0PR10MB5488.namprd10.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1233 bytes --]
On Sun, Sep 26, 2021 at 11:53 AM Drew Adams <drew.adams@oracle.com> wrote:
>
> > I noticed the following messages triggered frequently by Emacs:
> >
> > File mode specification error: (error Variable binding depth exceeds
> > max-specpdl-size)
> > Emacs: nesting exceeds `max-lisp-eval-depth'
> >
> > Any hints/suggestions or rule of thumb to set these variables?
>
> You generally shouldn't need to change them.
> You're likely coding an infinite recursion, so
> the stack overflows. Check your code - or
> narrow the problem down to some bit of code
> and post it here, if you can't see how/why
> you've cause an infinite recursion.
I set the following line in ~/.emacs.d/init.el:
(setq debug-on-error t)
Then a python file with the following content is opened in Emacs:
import matplotlib.pyplot as plt
from numpy import arange, p(*)i, sin
from sympy import Symbol, integrate
t = arange(0, 2*pi, .01)
plt.plot(sin(4*t), sin(5*t))
x = Symbol('x')
integrate(1/(1+x**3))
Now, I put point on `p' of `pi', denoted by * above. And hit
`M-.' which runs the command xref-find-definitions. The error shown in
the attachment will be triggered. When I hit the `M-.' for the second
time, it will be executed successfully.
Regards, HZ
[-- Attachment #2: max-specpdl-size.png --]
[-- Type: image/png, Size: 190265 bytes --]
prev parent reply other threads:[~2021-09-26 7:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-26 1:48 `max-specpdl-size' and `max-lisp-eval-depth' Hongyi Zhao
2021-09-26 2:36 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-09-26 6:33 ` Hongyi Zhao
2021-09-26 7:13 ` tomas
2021-09-26 11:26 ` Hongyi Zhao
2021-09-26 11:55 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-09-26 13:04 ` Eli Zaretskii
2021-09-26 15:01 ` Hongyi Zhao
2021-09-28 10:50 ` Stephen Berman
2021-09-28 11:03 ` Hongyi Zhao
2021-09-28 11:05 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-09-28 11:20 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-09-28 13:49 ` tomas
2021-09-28 14:08 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-09-28 14:19 ` tomas
2021-09-28 11:14 ` Lars Ingebrigtsen
2021-09-28 11:23 ` Stephen Berman
2021-09-29 5:53 ` Lars Ingebrigtsen
2021-09-26 3:53 ` [External] : " Drew Adams
2021-09-26 4:09 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-09-28 3:45 ` Google vi (was: Re: [External] : `max-specpdl-size' and `max-lisp-eval-depth') Emanuel Berg via Users list for the GNU Emacs text editor
2021-09-26 7:09 ` Hongyi Zhao [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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAGP6POLwPP49y+EyDghDwrGFy5Skpp8pUdhkYfxxBa5wn1+Pyw@mail.gmail.com \
--to=hongyi.zhao@gmail.com \
--cc=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).