From: Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: eudc fails with bbdb
Date: Thu, 14 Apr 2005 10:40:43 -0400 [thread overview]
Message-ID: <874qe9xw2u.fsf-monnier+gnu.emacs.help@gnu.org> (raw)
In-Reply-To: m2wtr5r44b.fsf@seki.fr
> Debugger entered--Lisp error: (invalid-function (macro lambda (vector) (list (quote aref) vector 4)))
Such an error is almost invariably due to a miscompiled file (either
because a file was not recompiled or because of a missing `require'
statement, ...).
In your case it seems the miscompiled code is in eudc-bbdb-extract-phones
where it uses the macro bbdb-record-phones.
Stefan
next prev parent reply other threads:[~2005-04-14 14:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-14 11:26 eudc fails with bbdb Sébastien Kirche
2005-04-14 14:40 ` Stefan Monnier [this message]
2005-04-14 15:47 ` Sébastien Kirche
2005-04-15 13:28 ` Stefan Monnier
2005-04-15 14:57 ` Sébastien Kirche
2005-04-15 15:53 ` Stefan Monnier
2005-04-15 16:42 ` Sébastien Kirche
2005-04-16 4:11 ` Stefan Monnier
2005-04-14 15:38 ` Kevin Rodgers
[not found] ` <mailman.1508.1113493483.2895.help-gnu-emacs@gnu.org>
2005-04-14 15:56 ` Sébastien Kirche
2005-04-14 22:33 ` Kevin Rodgers
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=874qe9xw2u.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).