From: Tassilo Horn <tassilo@member.fsf.org>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 8510@debbugs.gnu.org
Subject: bug#8510: 24.0.50; lexbind problem (apparently): void-variable symbol
Date: Sat, 16 Apr 2011 19:36:45 +0200 [thread overview]
Message-ID: <87d3km5c9e.fsf@member.fsf.org> (raw)
In-Reply-To: <B8A4C5D4D3AE4E399E2BE34075E5D809@us.oracle.com> (Drew Adams's message of "Sat, 16 Apr 2011 09:58:51 -0700")
"Drew Adams" <drew.adams@oracle.com> writes:
Hi Drew,
>> Your description sounds very similar to an issue I had with
>> anything.el when switching to the (now merged) lexbind branch.
>> The issue was that some advice tried to access one arg of the
>> adviced function by its name.
>
> You might be right that it is in my code (dunno), but if so I don't
> think it has to do with the problem you mention. The problem you
> mention is, I think, bug #8457 (which has reportedly been fixed, BTW).
Yes, right.
> I do not use defadvice in this way in my code anywhere (anymore) - I
> use only `ad-get-arg'. And in the Icicles code I use defadvice in
> only two minor places, neither of which accesses an argument (by name
> or otherwise).
Yes, the code can be anywhere. For me, the problem was in anything, but
the symptom occured also with M-x describe-*. I'd grep thru all elisp
files I have installed for defadvices and check them.
Bye,
Tassilo
next prev parent reply other threads:[~2011-04-16 17:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-16 15:44 bug#8510: 24.0.50; lexbind problem (apparently): void-variable symbol Drew Adams
2011-04-16 16:33 ` Tassilo Horn
2011-04-16 16:58 ` Drew Adams
2011-04-16 17:36 ` Tassilo Horn [this message]
2011-04-16 18:01 ` Drew Adams
2011-04-18 19:15 ` Stefan Monnier
2011-04-19 13:30 ` Stefan Monnier
2011-04-19 13:52 ` Drew Adams
2013-02-23 1:01 ` Glenn Morris
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=87d3km5c9e.fsf@member.fsf.org \
--to=tassilo@member.fsf.org \
--cc=8510@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 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.