I see similar problems (not involving speedbar), I wish I knew why.
andy
-----Original Message-----
From: xemacs-beta-admin(a)xemacs.org
[mailto:xemacs-beta-adminï¼ xemacs.org]On Behalf Of Dr. Volker Zell
Sent: Monday, November 19, 2001 4:20 PM
To: xemacs-beta(a)xemacs.org
Subject: Problem instrumenting defuns for debugging when running
speedbar
Hi
When trying to call
Instrument This Defun For Debugging
from the right mouse popup-menu inside of a lisp file I get the
following messages
and stacktrace when running speedbar in another frame. This
happens only when trying
for the first time. From then on I can succesfully instrument:
Loading edebug...
Loading edebug...done
Symbol's value as variable is void: speedbar-with-writable
Signaling: (void-variable speedbar-with-writable)
#<compiled-function nil "...(5)" [def-body
speedbar-with-writable def-edebug-spec] 3>()
run-hooks(#<compiled-function nil "...(5)" [def-body
speedbar-with-writable def-edebug-spec] 3>)
edebug-read-and-maybe-wrap-form()
edebug-read-top-level-form()
#<compiled-function nil "...(10)" [eval t edebug-all-defs
edebug-all-forms edebug-read-top-level-form] 3
("/usr/local/lib/xemacs/xemacs-packages/lisp/edebug/edebug.elc" .
13819) nil>()
call-interactively(edebug-defun)
menu-call-at-event(edebug-defun)
eval((menu-call-at-event (quote edebug-defun)))
dispatch-event(#<misc-user-event (eval (menu-call-at-event
(quote edebug-defun)))>)
popup-mode-menu(#<buttondown-event button3>)
call-interactively(popup-mode-menu)
Any idea ??
Ciao
Volker