From: Lars Ingebrigtsen <larsi@gnus.org>
To: Ken Hori <fplemma@gmail.com>
Cc: 6892@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#6892: Please add a way to jump to advices
Date: Mon, 09 May 2022 18:41:52 +0200 [thread overview]
Message-ID: <87zgjq3bfz.fsf@gnus.org> (raw)
In-Reply-To: <AANLkTinU2RXwTN8_AeDh9t5gGdg3V5G+vrta+P67oxO3@mail.gmail.com> (Ken Hori's message of "Sat, 21 Aug 2010 11:17:21 -0700")
Ken Hori <fplemma@gmail.com> writes:
> There is describe-function and describe-variable, but no describe-advice.
>
> (describe-function 'foo) describes function foo, but if it's adviced it states
> "[t]his function is advised," along with its documentation -- but
> without a way to
> actually jump to its source.
(I'm going through old bug reports that unfortunately weren't resolved
at the time.)
This seems to still be the case with advice-add:
(defun bar ()
(interactive)
(forward-line 1))
(advice-add 'bar :before (lambda () (forward-line 1)))
leads to:
---
bar is an interactive Lisp function in ‘/tmp/ad.el’.
(bar)
This function has :before advice: No documentation
---
And no links to the advice.
I'm sure this has come up before -- does advice add no pointers (to
load-history, I guess?) that the help system could pick up?
Or has that been considered and rejected before?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-05-09 16:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-21 18:17 bug#6892: Please add a way to jump to advices Ken Hori
2022-05-09 16:41 ` Lars Ingebrigtsen [this message]
2022-05-09 16:50 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-10 2:01 ` Lars Ingebrigtsen
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=87zgjq3bfz.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=6892@debbugs.gnu.org \
--cc=fplemma@gmail.com \
--cc=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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).