bug#13085: 24.3.50; (invalid-function internal--called-interactively-p--get-frame)

all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed

From: "Drew Adams" <drew.adams@oracle.com>
To: "'Dani Moncayo'" <dmoncayo@gmail.com>
Cc: 13085@debbugs.gnu.org, nyc4bos@aol.com
Subject: bug#13085: 24.3.50; (invalid-function internal--called-interactively-p--get-frame)
Date: Fri, 7 Dec 2012 12:51:07 -0800	[thread overview]
Message-ID: <85451309C4B64927B5B1730C11F11A76@us.oracle.com> (raw)
In-Reply-To: <F7E5B6AEA6184E83BA37DB5B00593C81@us.oracle.com>

> Sorry, I don't have a recipe.  I have no idea what's going 
> on.  Perhaps Stefan has an idea.  Note that someone else
> reported the same bug (as #13097).

I can consistently get it to happen by, after loading my setup (which uses
byte-compiled files), loading one of the source files *.el whose .elc was
loaded.

But attempts to bifurcate that file to see what might be going on have failed.
It seems unpredictable which portions of the file can trigger the problem.

Without finding some specific bit of code that would also repro the pb outside
my setup, I'm afraid we'll just have to wait for the next build and see if
perhaps that fixes the problem.

next prev parent reply	other threads:[~2012-12-07 20:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-05  0:44 bug#13085: 24.3.50; (invalid-function internal--called-interactively-p--get-frame) Drew Adams
2012-12-05  4:13 ` Stefan Monnier
2012-12-05  4:19   ` Drew Adams
2012-12-05  4:59     ` Stefan Monnier
2012-12-07 17:27       ` Drew Adams
2012-12-07 18:40         ` Dani Moncayo
2012-12-07 18:55           ` Drew Adams
2012-12-07 20:51             ` Drew Adams [this message]
2012-12-07 21:36           ` Stefan Monnier
2012-12-07 21:42             ` Eli Zaretskii
2012-12-07 20:31       ` nyc4bos
2012-12-07 21:29         ` Dani Moncayo
2012-12-07 22:19           ` Drew Adams
2012-12-10 22:53             ` nyc4bos

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=85451309C4B64927B5B1730C11F11A76@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=13085@debbugs.gnu.org \
    --cc=dmoncayo@gmail.com \
    --cc=nyc4bos@aol.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.