Sorry, not reproducible so far but I&#39;ve seen it on many files. rg-mac.el is my file of Mac OSX specific customizations.<br><br>You can see from the code I cited however that if that var is ever set to a dead-frame, you&#39;ll have the problem.<br>

<br>If I run into a reproducible case, I&#39;ll certainly send it on.<br><br>Thanks for looking into it.<br><br>-Rob<br><br><div class="gmail_quote">On Sat, Nov 7, 2009 at 1:24 PM, Chong Yidong <span dir="ltr">&lt;<a href="mailto:cyd@stupidchicken.com">cyd@stupidchicken.com</a>&gt;</span> wrote:<br>

<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">&gt; 1) created second frame<br>
&gt; 2) killed second frame after some random editing<br>
&gt; 3) in first frame, on attempt to kill buffer saw:<br>
&gt;<br>
&gt; menu-bar-non-minibuffer-window-p: Wrong type argument: frame-live-p, #&lt;dead<br>
&gt; frame [Gnu/Linux:robcvm] /home/rgiardina/emacs/rg-mac.el 0xaedc088&gt;<br>
<br>
What is this rg-mac.el file supposed to be doing?  It&#39;s a little hard to<br>
debug your custom code if we don&#39;t know how it&#39;s triggered.  Please<br>
provide a self-contained recipe for reproducing this bug.  Thanks.<br>
<br>
</blockquote></div><br>