[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: menu-bar-update-hook performance problems
From: |
Kai Großjohann |
Subject: |
Re: menu-bar-update-hook performance problems |
Date: |
Mon, 03 Mar 2003 21:04:25 +0100 |
User-agent: |
Gnus/5.090016 (Oort Gnus v0.16) Emacs/21.3.50 (i686-pc-linux-gnu) |
Dan Debertin <airboss@nodewarrior.org> writes:
> o How to instrument built-in functions for Edebug, so I can get a
> backtrace and figure out what's calling
> (run-hooks 'menu-bar-update-hook). The documentation says that
> you have to re-evaluate the defun with C-u C-M-x, but I obviously
> can't do that with built-ins. Right?
It's much easier: put your own function on the hook that invokes
(debug). From there you can examine the backtrace and then continue.
Hm. OTOH, whether this simple approach works for
menu-bar-update-hook, of all places, I'm not so sure. Invoking the
debugger changes the menu bar...
--
A preposition is not a good thing to end a sentence with.
Re: menu-bar-update-hook performance problems, Kevin Rodgers, 2003/03/04