all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Marcin Borkowski <mbork@mbork.pl>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Can an :around advice know the name of the function it is advising?
Date: Sun, 14 Feb 2016 19:47:48 +0100	[thread overview]
Message-ID: <87h9hb2kob.fsf@mbork.pl> (raw)
In-Reply-To: <87twlb9sn4.fsf@web.de>


On 2016-02-14, at 17:13, Michael Heerdegen <michael_heerdegen@web.de> wrote:

> Marcin Borkowski <mbork@mbork.pl> writes:
>
>> I would like to be able for an :around advice to know not only the
>> "original function" it is supposed to call, but also its /name/.  (Yes,
>> I now a function need not have /one/ name -- it may have more or less --
>> but assume that I added the advice to a command having one name in
>> a usual manner.)  Is it even possible?  (I guess not, but I wanted to
>> make sure.)
>
> If you know a name of the function you want to advice, you can make it
> known to the piece of advice too, of course ;-) But no, there is no

Yes, and as you have seen in my other message (thanks for the answer,
I'll reply later) I went that route.

> special mechanism for finding the name of the advised function from
> within the advice code AFAIK - apart from looking at the
> `backtrace-frame's or other brutal things.
>
> AFAICT the process of installing advises only touches functions, but
> doesn't cause changes on the symbol level apart from the functions
> fbound to them.

Thanks.

> Michael.

Best,

-- 
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Faculty of Mathematics and Computer Science
Adam Mickiewicz University



      parent reply	other threads:[~2016-02-14 18:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-14  8:02 Can an :around advice know the name of the function it is advising? Marcin Borkowski
2016-02-14 16:13 ` Michael Heerdegen
2016-02-14 16:40   ` Michael Heerdegen
2016-02-14 18:47   ` Marcin Borkowski [this message]

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=87h9hb2kob.fsf@mbork.pl \
    --to=mbork@mbork.pl \
    --cc=help-gnu-emacs@gnu.org \
    --cc=michael_heerdegen@web.de \
    /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.