GNU bug report logs - #8184
23.1.90; `menu-bar-non-minibuffer-window-p' error in calls to `kill-this-buffer'

Previous Next

Full log

Message #8 received at 8184 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: tlh <thunkout <at> gmail.com>
Cc: 8184 <at> debbugs.gnu.org
Subject: Re: bug#8184: 23.1.90;
	`menu-bar-non-minibuffer-window-p' error in calls to
	`kill-this-buffer'
Date: Sun, 06 Mar 2011 07:45:56 -0500

> From: tlh <thunkout <at> gmail.com>
> Date: Sat, 05 Mar 2011 23:28:31 -0600
> Cc: 
> 
> 
> `menu-updating-frame' is pointing to a dead frame, causing a
> `frame-live-p' error in `menu-bar-non-minibuffer-p' when I call
> `kill-this-buffer'.  I don't how it got out of sync, but it seems to me
> that `kill-this-buffer' shouldn't be in menu-bar.el -- or depend on
> menu-bar-specific code -- in the first place.

??? This function is bound to the "Close" item in the "File" menu, so
it is definitely related to the menu bar.

> Backtrace:
> 
> Debugger entered--Lisp error: (wrong-type-argument frame-live-p #<dead frame *Help* 0x100d1e930>)
>   frame-selected-window(#<dead frame *Help* 0x100d1e930>)
>   menu-bar-non-minibuffer-window-p()
>   kill-this-buffer()
>   call-interactively(kill-this-buffer nil nil)

Did you call kill-this-buffer from the menu bar, or with M-x?

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.