GNU bug report logs - #31793
26.1; (error "Lisp nesting exceeds ‘max-lisp-eval-depth’")

Previous Next

Package: emacs;

Reported by: Leo Liu <sdl.web <at> gmail.com>

Date: Tue, 12 Jun 2018 02:33:02 UTC

Severity: normal

Tags: fixed

Found in version 26.1

Fixed in version 26.2

Done: Noam Postavsky <npostavs <at> gmail.com>

Bug is archived. No further changes may be made.

Full log

Message #29 received at 31793 <at> debbugs.gnu.org (full text, mbox):

From: Leo Liu <sdl.web <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 31793 <at> debbugs.gnu.org
Subject: Re: bug#31793: 26.1; (error "Lisp nesting exceeds	‘max-lisp-eval-depth’")
Date: Tue, 12 Jun 2018 16:46:11 +0800

[Message part 1 (text/plain, inline)]
On 2018-06-12 08:21 +0300, Eli Zaretskii wrote:
> Ugh, macOS...  This means no xbacktrace and no other GDB
> wizardry...

Indeed.

> Well, I think the most important thing is to produce a Lisp
> backtrace from the error.

Turns out 26.1 cannot load a version of python.el (by dave love) that I
have in my site-lisp.

1. emacs -Q -l python.el
2. M-x python-mode

,----[ error ]
| Variable binding depth exceeds max-specpdl-size
| Error in post-command-hook (global-eldoc-mode-check-buffers): (error "Variable binding depth exceeds max-specpdl-size")
`----

Gnus was just loading python-mode to fontify some code in an article.


[python.el (application/emacs-lisp, attachment)]
This bug report was last modified 7 years and 9 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.