From: Dmitry Gutov <dgutov@yandex.ru>
To: Michael Albinus <michael.albinus@gmx.de>,
Phil Sainty <psainty@orcon.net.nz>
Cc: 27397@debbugs.gnu.org
Subject: bug#27397: [PATCH] New commands for bulk tracing of elisp functions
Date: Mon, 19 Jun 2017 14:27:43 +0300 [thread overview]
Message-ID: <25ce7f3c-6f70-82f1-b3fb-7dd7362bbdf2@yandex.ru> (raw)
In-Reply-To: <871sqg5mig.fsf@detlef>
Hi Michael,
On 6/19/17 12:56 PM, Michael Albinus wrote:
> That's not what I want. Often, I hunt bugs related to the order of
> autoloaded functions, and this order shall be kept also when tracing.
Your case is surely valid, but sounds a bit niche to me. It shouldn't be
too hard to evaluate this, though:
(with-eval-after-load 'tramp
(trace-package "tramp-"))
And the current patch makes it easier.
>> Perhaps you're actually be suggesting some kind of `eval-after-load'
>> tracing behaviour, though?
>
> Yes, that's the idea. If `trace-package' uses as argument a package name
> as proposed above, the instrumentation shall happen in an
> `eval-after-load' form for that package.
Considering elp-instrument-package does not do that, I think we should
limit the scope of the currently discussed patch, and trace only already
loaded functions.
If we do what you suggest, it should be a new discussion, and it should
improve elp-instrument-package as well.
next prev parent reply other threads:[~2017-06-19 11:27 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-16 13:32 bug#27397: [PATCH] New commands for bulk tracing of elisp functions Phil Sainty
2017-06-16 14:58 ` Dmitry Gutov
2017-06-17 8:43 ` Phil Sainty
2017-06-17 9:13 ` Dmitry Gutov
2017-06-19 7:45 ` Michael Albinus
2017-06-19 9:35 ` Phil Sainty
2017-06-19 9:56 ` Michael Albinus
2017-06-19 11:00 ` Phil Sainty
2017-06-19 12:05 ` Michael Albinus
2017-06-19 12:17 ` Phil Sainty
2017-06-19 12:50 ` Dmitry Gutov
2017-06-19 13:07 ` Michael Albinus
2017-06-19 11:27 ` Dmitry Gutov [this message]
2017-06-19 11:36 ` Michael Albinus
2017-06-19 12:04 ` Dmitry Gutov
2017-06-19 12:08 ` Michael Albinus
2017-06-19 12:24 ` Phil Sainty
2017-06-16 15:43 ` Kaushal Modi
2017-06-17 8:48 ` Phil Sainty
2017-06-17 9:20 ` Phil Sainty
2017-06-17 12:31 ` Phil Sainty
2017-06-17 22:59 ` Dmitry Gutov
2017-06-18 1:06 ` Phil Sainty
2017-06-18 6:32 ` Dmitry Gutov
2017-06-18 11:22 ` Phil Sainty
2019-06-27 18:01 ` bug#1343: " Lars Ingebrigtsen
2019-06-28 11:25 ` bug#27397: " Phil Sainty
2021-04-17 5:51 ` bug#1343: [PATCH] trace package Stefan Kangas
2021-04-17 14:01 ` bug#27397: " Phil Sainty
2021-10-21 20:29 ` Stefan Kangas
2022-07-15 4:08 ` bug#27397: bug#1343: bug#27397: [PATCH] New commands for bulk tracing of elisp functions Phil Sainty
2022-07-15 6:23 ` Eli Zaretskii
2022-07-15 11:09 ` Phil Sainty
2022-09-11 11:49 ` Lars Ingebrigtsen
2022-09-11 12:33 ` Eli Zaretskii
2022-09-12 13:26 ` Michael Albinus
2022-09-12 22:17 ` bug#1343: " Phil Sainty
2022-09-13 7:34 ` bug#27397: " Michael Albinus
2022-09-13 11:11 ` Lars Ingebrigtsen
2017-06-17 23:03 ` Dmitry Gutov
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=25ce7f3c-6f70-82f1-b3fb-7dd7362bbdf2@yandex.ru \
--to=dgutov@yandex.ru \
--cc=27397@debbugs.gnu.org \
--cc=michael.albinus@gmx.de \
--cc=psainty@orcon.net.nz \
/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).