From: kai.grossjohann@uni-duisburg.de (Kai Großjohann)
Subject: Re: menu-bar-update-hook performance problems
Date: Tue, 04 Mar 2003 09:06:38 +0100 [thread overview]
Message-ID: <84vfyzo8s1.fsf@lucy.is.informatik.uni-duisburg.de> (raw)
In-Reply-To: 84adgctdx2.fsf@lucy.is.informatik.uni-duisburg.de
kai.grossjohann@uni-duisburg.de (Kai Großjohann) writes:
> 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...
Another idea: put a function on menu-bar-update-hook that let-binds
menu-bar-update-hook to nil, then invokes (debug).
Maybe it works.
--
A preposition is not a good thing to end a sentence with.
next prev parent reply other threads:[~2003-03-04 8:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-03 18:04 menu-bar-update-hook performance problems Dan Debertin
2003-03-03 20:04 ` Kai Großjohann
2003-03-03 22:23 ` Dan Debertin
2003-03-04 8:07 ` Kai Großjohann
2003-03-04 15:44 ` Dan Debertin
2003-03-04 17:55 ` Kai Großjohann
2003-03-10 19:53 ` Stefan Monnier
2003-03-04 8:06 ` Kai Großjohann [this message]
2003-03-04 20:06 ` Kevin Rodgers
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=84vfyzo8s1.fsf@lucy.is.informatik.uni-duisburg.de \
--to=kai.grossjohann@uni-duisburg.de \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).