all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Rob Giardina <rob@socialfact.com>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: 4856@emacsbugs.donarmstrong.com
Subject: bug#4856: 23.1.50; menu-updating-frame stays set to dead frame
Date: Sat, 7 Nov 2009 13:28:12 -0500	[thread overview]
Message-ID: <275d7f050911071028p26f761c3mf2aeb1bf609ab9d8@mail.gmail.com> (raw)
In-Reply-To: <87aayychvt.fsf@stupidchicken.com>

[-- Attachment #1: Type: text/plain, Size: 923 bytes --]

Sorry, not reproducible so far but I've seen it on many files. rg-mac.el is
my file of Mac OSX specific customizations.

You can see from the code I cited however that if that var is ever set to a
dead-frame, you'll have the problem.

If I run into a reproducible case, I'll certainly send it on.

Thanks for looking into it.

-Rob

On Sat, Nov 7, 2009 at 1:24 PM, Chong Yidong <cyd@stupidchicken.com> wrote:

> > 1) created second frame
> > 2) killed second frame after some random editing
> > 3) in first frame, on attempt to kill buffer saw:
> >
> > menu-bar-non-minibuffer-window-p: Wrong type argument: frame-live-p,
> #<dead
> > frame [Gnu/Linux:robcvm] /home/rgiardina/emacs/rg-mac.el 0xaedc088>
>
> What is this rg-mac.el file supposed to be doing?  It's a little hard to
> debug your custom code if we don't know how it's triggered.  Please
> provide a self-contained recipe for reproducing this bug.  Thanks.
>
>

[-- Attachment #2: Type: text/html, Size: 1293 bytes --]

  reply	other threads:[~2009-11-07 18:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-07 18:24 bug#4856: 23.1.50; menu-updating-frame stays set to dead frame Chong Yidong
2009-11-07 18:28 ` Rob Giardina [this message]
2011-09-11  4:54   ` Lars Magne Ingebrigtsen
  -- strict thread matches above, loose matches on Subject: below --
2009-11-02 20:12 Rob Giardina

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=275d7f050911071028p26f761c3mf2aeb1bf609ab9d8@mail.gmail.com \
    --to=rob@socialfact.com \
    --cc=4856@emacsbugs.donarmstrong.com \
    --cc=cyd@stupidchicken.com \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.