From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Dan Debertin Newsgroups: gmane.emacs.help Subject: Re: menu-bar-update-hook performance problems Date: 03 Mar 2003 16:23:09 -0600 Sender: help-gnu-emacs-bounces+gnu-help-gnu-emacs=m.gmane.org@gnu.org Message-ID: <87d6l8ozsi.fsf@nodewarrior.org> References: <87llzws4wz.fsf@nodewarrior.org> <84adgctdx2.fsf@lucy.is.informatik.uni-duisburg.de> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: main.gmane.org 1046730539 3495 80.91.224.249 (3 Mar 2003 22:28:59 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 3 Mar 2003 22:28:59 +0000 (UTC) Return-path: Original-Received: from monty-python.gnu.org ([199.232.76.173]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 18pyQa-0000uC-00 for ; Mon, 03 Mar 2003 23:28:57 +0100 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.10.13) id 18pyO4-0003fH-01 for gnu-help-gnu-emacs@m.gmane.org; Mon, 03 Mar 2003 17:26:20 -0500 Original-Path: shelby.stanford.edu!newsfeed.stanford.edu!news.uchicago.edu!logbridge.uoregon.edu!feed2.news.rcn.net!rcn!news-out.visi.com!hermes.visi.com!gemini.bitstream.net.POSTED!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 27 Original-NNTP-Posting-Host: 0538614c.news.bitstream.net Original-X-Trace: 1046730306 gemini.bitstream.net 22477 216.243.168.26 Original-X-Complaints-To: abuse@bitstream.net Original-Xref: shelby.stanford.edu gnu.emacs.help:110767 Original-To: help-gnu-emacs@gnu.org X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1b5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , Errors-To: help-gnu-emacs-bounces+gnu-help-gnu-emacs=m.gmane.org@gnu.org Xref: main.gmane.org gmane.emacs.help:7268 X-Report-Spam: http://spam.gmane.org/gmane.emacs.help:7268 kai.grossjohann@uni-duisburg.de (Kai Großjohann) writes: > 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... So you see my dilemma :). Updating the mode-line also calls menu-bar-update-hook, so anything that touches the mode-line is also off-limits. My next trick was to add this to the head of menu-bar-update-hook: (lambda () (save-excursion (set-buffer (get-buffer-create "*temp-trace*")) (insert (prin1-to-string (backtrace)))))) But, sadly, the backtraces I get out of it (and boy, do I ever get backtraces) stop at 'run-hooks'. Perhaps I will advise run-hooks. Dan -- /^Dan Debertin$/ | airboss@nodewarrior.org | www.nodewarrior.org |