From: "Drew Adams" <drew.adams@oracle.com>
To: "'Tassilo Horn'" <tassilo@member.fsf.org>
Cc: 8510@debbugs.gnu.org
Subject: bug#8510: 24.0.50; lexbind problem (apparently): void-variable symbol
Date: Sat, 16 Apr 2011 11:01:50 -0700 [thread overview]
Message-ID: <9C9B3E5B54934225B6CA1F7C0AA79E7D@us.oracle.com> (raw)
In-Reply-To: <87d3km5c9e.fsf@member.fsf.org>
> > 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.
Yes, I did that. That's what I meant by "I do not use defadvice in this way in
my code anywhere (anymore) - I use only `ad-get-arg'." By "anywhere" I meant in
_any_ of my code.
None of my code (or other 3rd-party code that I load) uses defadvice with a
named argument. It uses only `ad-get-arg' when it accesses arguments.
And the Icicles code, which is the code invoking the call to
`documentation-property' that raises the error, has only two defadvices, neither
of which accesses any argument.
So it seems to me that this bug is unrelated to #8457.
But I could be wrong, of course.
next prev parent reply other threads:[~2011-04-16 18:01 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
2011-04-16 18:01 ` Drew Adams [this message]
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=9C9B3E5B54934225B6CA1F7C0AA79E7D@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=8510@debbugs.gnu.org \
--cc=tassilo@member.fsf.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.