From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Fabrice Niessen" <fni@missioncriticalit.com>
Cc: 13252@debbugs.gnu.org, Bastien <bzg@altern.org>,
public-13252-ubl+/3LiMTaZdePnXv/OxA@plane.gmane.org,
Fabrice Niessen
<public-fni-djc/iPCCuDYQheJpep6IedvLeJWuRmrY@plane.gmane.org>
Subject: bug#13252: must load a package before instrumenting it with elp
Date: Sun, 06 Feb 2022 01:01:36 +0100 [thread overview]
Message-ID: <878ruo982n.fsf_-_@gnus.org> (raw)
In-Reply-To: <80wqwa2p4d.fsf@somewhere.org> (Fabrice Niessen's message of "Sat, 22 Dec 2012 14:27:46 +0100")
"Fabrice Niessen" <fni@missioncriticalit.com> writes:
> That seems to be it. So, per se, it's not a bug.
>
> Though, we could imagine a better behavior of `elp-instrument-package' when
> instrumenting a non-yet required package; for example:
>
> - be warned that it's not possible at that stage, or
>
> - remember to instrument the package as soon it's required (somehow like an
> `eval-after-load'), or
>
> - requiring it when instrumenting it.
(I'm going through old bug reports that unfortunately weren't resolved
at the time.)
I think the way it currently works makes sense (that is, you can tell
which functions get instrumented easily), but the name of the function
seems to imply that it's doing something grander. So I've noted how it
actually works in the doc string in Emacs 29.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-02-06 0:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-22 10:08 bug#13252: 24.2.91; ELP Fabrice Niessen
2012-12-22 11:36 ` Bastien
[not found] ` <mailman.15913.1356176276.855.bug-gnu-emacs@gnu.org>
[not found] ` <mailman.15913.1356176276.855.bug-gnu-emacs-mXXj517/zsQ@public.gmane.org>
2012-12-22 13:27 ` Fabrice Niessen
2022-02-06 0:01 ` Lars Ingebrigtsen [this message]
2012-12-22 16:14 ` Stefan Monnier
2012-12-23 14:21 ` Michael Heerdegen
2020-11-26 0:52 ` Stefan Kangas
2020-11-26 1:22 ` Michael Heerdegen
[not found] ` <mailman.15927.1356192953.855.bug-gnu-emacs@gnu.org>
2012-12-22 21:18 ` Sebastien Vauban
2012-12-23 13:55 ` Stefan Monnier
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=878ruo982n.fsf_-_@gnus.org \
--to=larsi@gnus.org \
--cc=13252@debbugs.gnu.org \
--cc=bzg@altern.org \
--cc=fni@missioncriticalit.com \
--cc=public-13252-ubl+/3LiMTaZdePnXv/OxA@plane.gmane.org \
--cc=public-fni-djc/iPCCuDYQheJpep6IedvLeJWuRmrY@plane.gmane.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 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).