unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>
Cc: 19728@debbugs.gnu.org
Subject: bug#19728: 25.0.50; (wrong-type-argument frame-live-p #<dead frame *scratch* 0b54c8d8>)
Date: Thu, 29 Jan 2015 09:46:35 -0800 (PST)	[thread overview]
Message-ID: <252d43e8-3cc9-4a3f-960a-b7378a66305c@default> (raw)
In-Reply-To: <<83egqdmqs7.fsf@gnu.org>>

> Any idea how come redisplay got to call
> menu-bar-non-minibuffer-window-p?

I do have this in my setup - these are the only occurrences of
that function in my code:

;; Add for Emacs < 22.  Rename item otherwise.
(define-key menu-bar-file-menu [new-file]
  '(menu-item "New File..." find-file
    :enable (or (not (fboundp 'menu-bar-non-minibuffer-window-p))
             (menu-bar-non-minibuffer-window-p))
    :help "Create and edit a new file"))

(define-key-after menu-bar-file-menu [new-directory]
  '(menu-item "New Directory..." menu-bar-create-directory
    :enable (or (not (fboundp 'menu-bar-non-minibuffer-window-p))
             (menu-bar-non-minibuffer-window-p))
    :help "Create a directory")
  'new-file)

I realize that :enable will cause that code to be run during
redisplay.  Probably this is the culprit code, but I have never
see that error before (and this code has been there a long time).

So maybe it's just a one-off thing.





       reply	other threads:[~2015-01-29 17:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <<2fd82743-d6a0-482d-86e9-ac5cfd0d2271@default>
     [not found] ` <<83egqdmqs7.fsf@gnu.org>
2015-01-29 17:46   ` Drew Adams [this message]
2015-01-31 13:29     ` bug#19728: 25.0.50; (wrong-type-argument frame-live-p #<dead frame *scratch* 0b54c8d8>) Eli Zaretskii
2015-01-31 14:22       ` martin rudalics
2015-01-31 15:40         ` Eli Zaretskii
2015-01-31 18:46           ` martin rudalics
2015-01-31 18:59             ` Eli Zaretskii
2015-02-13 18:31               ` martin rudalics
2015-01-29 17:29 Drew Adams
2015-01-29 17:37 ` Eli Zaretskii

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=252d43e8-3cc9-4a3f-960a-b7378a66305c@default \
    --to=drew.adams@oracle.com \
    --cc=19728@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /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 public inbox

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

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).