From: Dani Moncayo <dmoncayo@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: 13085@debbugs.gnu.org
Subject: bug#13085: 24.3.50; (invalid-function internal--called-interactively-p--get-frame)
Date: Fri, 7 Dec 2012 19:40:02 +0100 [thread overview]
Message-ID: <CAH8Pv0hnA3YZSXMOX1hHYmmjMSvz429fk8-bL-0vUYLCngcc-w@mail.gmail.com> (raw)
In-Reply-To: <A9B0226E700D4A57A01BA4699654F782@us.oracle.com>
>> > OK, but my nadvice.elc is the one delivered with the Emacs binary
>> > I downloaded. I did not compile nadvice.el myself.
>>
>> I kind of guessed it, but that just pushes the question elsewhere.
>> IOW, we need to hear from those who built this binary.
>
> Any chance we could get a new Windows binary without this problem soon? This
> one is unusable.
Probably, I'll upload a new build on Monday.
FWIW:
* I've not bootstrapped Emacs for a while. So my last binaries are
compiled without bootstrapping.
* I've tried to reproduce your recipe in the OP, but I can't. I
evaluate the defadvice and then do `M-x ad-activate <RET> foo <RET>'
but `foo' is not a valid argument there. If you give me a precise
recipe, I'll try to reproduce the steps and see if the Lisp debugger
fires up.
--
Dani Moncayo
next prev parent reply other threads:[~2012-12-07 18:40 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 [this message]
2012-12-07 18:55 ` Drew Adams
2012-12-07 20:51 ` Drew Adams
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
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=CAH8Pv0hnA3YZSXMOX1hHYmmjMSvz429fk8-bL-0vUYLCngcc-w@mail.gmail.com \
--to=dmoncayo@gmail.com \
--cc=13085@debbugs.gnu.org \
--cc=drew.adams@oracle.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 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).