[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: |
Fri, 2 Apr 2021 08:49:31 +0200 |
> Do you have some extra info about how to reproduce this?
> I tried `M-x eval-buffer` inside `lisp/window.el` but that didn't signal
> any problem, neither before nor after loading `edebug.el`.
Suppose I put point within a function like `window-min-pixel-height' and
then type C-M-# which here
runs the command edebug-defun (found in edebug-mode-map), which is
an alias for ‘edebug-eval-top-level-form’ in ‘edebug.el’.
insert (window-min-pixel-height) into *scratch* and do C-x e and debug
that call. When I now type M-# in window.el which here
runs the command eval-buffer (found in edebug-mode-map), which is an
interactive built-in function in ‘C source code’.
I get
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)
Quitting *Backtrace* - I have (debug-on-error t) - and typing M-# again
gets me that "error" again and again.
Three settings in my custom-set-variables section which might be related
are
'(edebug-on-error nil)
'(edebug-on-quit nil)
'(edebug-print-level 50)
martin