[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#47516: 28.0.50; void-variable edebug-all-defs
From: |
martin rudalics |
Subject: |
bug#47516: 28.0.50; void-variable edebug-all-defs |
Date: |
Wed, 31 Mar 2021 10:10:30 +0200 |
For decades I'm used to debug Lisp functions by calling `edebug-defun'.
To get rid of the debugging instrumentation I'm using `eval-buffer'. In
the not so distant past Emacs started to complain about this habit as
follows:
Debugger entered--Lisp error: (void-variable edebug-all-defs)
edebug-read-and-maybe-wrap-form1()
edebug-read-and-maybe-wrap-form()
edebug--read(read #<buffer window.el>)
apply(edebug--read read #<buffer window.el>)
#f(advice-wrapper :around read edebug--read)(#<buffer window.el>)
eval-buffer() ; Reading at buffer position 990
funcall-interactively(eval-buffer)
call-interactively(eval-buffer nil nil)
command-execute(eval-buffer)
I neither understand the error message nor why I should not be allowed
to evaluate the buffer in this situation.
martin
- bug#47516: 28.0.50; void-variable edebug-all-defs,
martin rudalics <=