From: "Drew Adams" <drew.adams@oracle.com>
To: 9570@debbugs.gnu.org
Subject: bug#9570: 24.0.50; "debug-on-entry: Definition of ... is not a list"
Date: Wed, 21 Sep 2011 20:48:20 -0700 [thread overview]
Message-ID: <04F2A67454BA4472B8CED5ACDA79EB2B@us.oracle.com> (raw)
emacs -Q
Load file fuzzy.el, available in the tar or zip here:
http://cx4a.org/software/auto-complete/#Downloads
(The file is small.)
M-x debug-on-entry isearch-message-prefix RET
raises this error:
debug-on-entry: Definition of isearch-message-prefix is not a list
The file is contains this advice:
(defadvice isearch-message-prefix (after fuzzy-isearch-message-prefix activate)
(if fuzzy-isearch
(setq ad-return-value (concat fuzzy-isearch-prefix ad-return-value))
ad-return-value))
I seem to vaguely recall some problem associated with lexbind, advice,
and the debugger (and perhaps byte-compiling?). But a search of the
Elisp manual and some bug reports turned up nothing. I thought that
such problems had already been ironed out, but perhaps not.
It's very hard to find the cause of such an error - even just locating
the code that leads to it is not easy. And it's not clear to me now
what a user can/should do about it. What's the deal? If there is
something that users must not do or must avoid, then please document it.
In GNU Emacs 24.0.50.1 (i386-mingw-nt5.1.2600)
of 2011-09-19 on 3249CTO
Windowing system distributor `Microsoft Corp.', version 5.1.2600
configured using `configure --with-gcc (4.5) --no-opt'
next reply other threads:[~2011-09-22 3:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-22 3:48 Drew Adams [this message]
2017-03-25 2:03 ` bug#9570: 24.0.50; "debug-on-entry: Definition of ... is not a list" npostavs
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=04F2A67454BA4472B8CED5ACDA79EB2B@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=9570@debbugs.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 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.