From: Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: Debugging byte compiled files
Date: Mon, 06 Mar 2006 03:51:17 -0500 [thread overview]
Message-ID: <878xroklei.fsf-monnier+gnu.emacs.help@gnu.org> (raw)
In-Reply-To: mailman.602.1141491264.5838.help-gnu-emacs@gnu.org
> pabbrev-command-hook-fail((invalid-function (macro . #[...
This class of errors means invariably that a call to macro F was
byte-compiled while Emacs didn't know that F was going to be defined as
a macro rather than a function.
I.e. the macro didn't exist yet.
Either because it's defined later in the file, or because of a missing
`require'.
Stefan
next prev parent reply other threads:[~2006-03-06 8:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.602.1141491264.5838.help-gnu-emacs@gnu.org>
2006-03-04 23:33 ` Debugging byte compiled files John Paul Wallington
2006-03-06 8:51 ` Stefan Monnier [this message]
2006-03-07 18:51 Phillip Lord
-- strict thread matches above, loose matches on Subject: below --
2006-03-07 18:48 Phillip Lord
2006-03-07 19:16 ` John Paul Wallington
2006-03-04 16:54 Phillip Lord
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=878xroklei.fsf-monnier+gnu.emacs.help@gnu.org \
--to=monnier@iro.umontreal.ca \
/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.
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).