From: Leo Liu <sdl.web@gmail.com>
To: 31793@debbugs.gnu.org
Subject: bug#31793: 26.1; (error "Lisp nesting exceeds ‘max-lisp-eval-depth’")
Date: Tue, 12 Jun 2018 10:32:16 +0800 [thread overview]
Message-ID: <m14li8n39r.fsf@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 490 bytes --]
I was reading news in GNUS and suddenly emacs started echoing in the
minibuffer:
Error in post-command-hook (global-eldoc-mode-check-buffers): (error "Variable binding depth exceeds max-specpdl-size")
After that I could not M-x or M-: or did much to investigate, only able
to copy the last part of *Messages* to a file (attached). Not sure if
this is useful.
But this bug might be interesting. It is new. A max-specpdl-size
automatically popped up while I was idly reading in GNUS.
[-- Attachment #2: bug.txt --]
[-- Type: text/plain, Size: 2805 bytes --]
Error in post-command-hook (global-eldoc-mode-check-buffers): (error "Variable binding depth exceeds max-specpdl-size")
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")
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")
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")
Quit [5 times]
Saving /Users/GNUS/.newsrc.eld...
Saving file /Users/GNUS/.newsrc.eld...
Wrote /Users/GNUS/.newsrc.eld
Saving /Users/GNUS/.newsrc.eld...done
Error in post-command-hook (global-eldoc-mode-check-buffers): (error "Variable binding depth exceeds max-specpdl-size")
completing-read-default: Lisp nesting exceeds ‘max-lisp-eval-depth’
Error in post-command-hook (global-eldoc-mode-check-buffers): (error "Variable binding depth exceeds max-specpdl-size")
byte-code: Lisp nesting exceeds ‘max-lisp-eval-depth’
Error in post-command-hook (global-eldoc-mode-check-buffers): (error "Variable binding depth exceeds max-specpdl-size")
Entering debugger...
Error in pre-command-hook (delete-selection-pre-hook): (error "Lisp nesting exceeds ‘max-lisp-eval-depth’")
Quit
Error in post-command-hook (global-eldoc-mode-check-buffers): (error "Variable binding depth exceeds max-specpdl-size")
completing-read-default: Lisp nesting exceeds ‘max-lisp-eval-depth’
Error in post-command-hook (global-eldoc-mode-check-buffers): (error "Variable binding depth exceeds max-specpdl-size")
let: Lisp nesting exceeds ‘max-lisp-eval-depth’
Error in post-command-hook (global-eldoc-mode-check-buffers): (error "Variable binding depth exceeds max-specpdl-size")
next-line: End of buffer
let: Lisp nesting exceeds ‘max-lisp-eval-depth’
Error in post-command-hook (global-eldoc-mode-check-buffers): (error "Variable binding depth exceeds max-specpdl-size")
next-line: End of buffer [18 times]
completing-read-default: Lisp nesting exceeds ‘max-lisp-eval-depth’
Error in post-command-hook (global-eldoc-mode-check-buffers): (error "Variable binding depth exceeds max-specpdl-size")
next-line: End of buffer [5 times]
python-args-to-list: 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")
next-line: End of buffer [7 times]
C-c C-k is undefined
ido-read-internal: Lisp nesting exceeds ‘max-lisp-eval-depth’
Error in post-command-hook (global-eldoc-mode-check-buffers): (error "Variable binding depth exceeds max-specpdl-size")
next reply other threads:[~2018-06-12 2:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-12 2:32 Leo Liu [this message]
2018-06-12 4:43 ` bug#31793: 26.1; (error "Lisp nesting exceeds ‘max-lisp-eval-depth’") Leo Liu
2018-06-12 4:59 ` Leo Liu
2018-06-12 5:21 ` Eli Zaretskii
2018-06-12 8:46 ` Leo Liu
2018-06-23 15:47 ` John Shahid
2018-06-24 8:27 ` Leo Liu
2018-06-25 13:59 ` John Shahid
2018-06-25 16:24 ` Noam Postavsky
2018-07-03 16:43 ` John Shahid
2018-07-04 22:38 ` Noam Postavsky
2018-07-05 13:59 ` Eli Zaretskii
2018-07-05 16:33 ` John Shahid
2018-07-10 12:17 ` Noam Postavsky
2018-06-12 5:04 ` Eli Zaretskii
2018-06-12 5:24 ` Leo Liu
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=m14li8n39r.fsf@gmail.com \
--to=sdl.web@gmail.com \
--cc=31793@debbugs.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.
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.