From: Marcin Borkowski <mbork@mbork.pl>
To: Noam Postavsky <npostavs@users.sourceforge.net>
Cc: Jean-Christophe Helary <jean.christophe.helary@gmail.com>,
Emacs-Devel devel <emacs-devel@gnu.org>
Subject: Re: debugging elisp ?
Date: Sun, 09 Jul 2017 13:59:15 +0200 [thread overview]
Message-ID: <878tjxx1m4.fsf@jane> (raw)
In-Reply-To: <CAM-tV-_=m5shR7S_b4x_P_8i11hBkxXAWn9B9rvRby+5VZVxig@mail.gmail.com>
On 2017-07-09, at 13:48, Noam Postavsky <npostavs@users.sourceforge.net> wrote:
> On Sun, Jul 9, 2017 at 6:49 AM, Jean-Christophe Helary
> <jean.christophe.helary@gmail.com> wrote:
>>
>> My limited understanding of the documentation tells me that I can't keep the debugger working during the whole package session. I can call it on package-list-packages and it will run until the package list is displayed, and then it quits.
>>
>> Does that mean that I have to mark all the package functions for debugging ?
>
> Yes, you can do that with the following code:
>
> (require 'edebug)
> (require 'package)
> (mapatoms (lambda (s) (and (fboundp s)
> (string-match-p "\\`package" (symbol-name s)))
> (edebug-instrument-function s)))
Won't
M-x edebug-all-defuns
and then
M-x eval-buffer
in package.el work as well (and be easier)?
Best,
--
Marcin Borkowski
next prev parent reply other threads:[~2017-07-09 11:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-09 8:03 debugging elisp ? Jean-Christophe Helary
2017-07-09 9:44 ` Marcin Borkowski
2017-07-09 10:49 ` Jean-Christophe Helary
2017-07-09 11:48 ` Noam Postavsky
2017-07-09 11:58 ` Jean-Christophe Helary
2017-07-09 11:59 ` Marcin Borkowski [this message]
2017-07-09 12:13 ` Noam Postavsky
2017-07-09 13:54 ` Jean-Christophe Helary
2017-07-10 13:31 ` Michael Heerdegen
2017-07-11 1:06 ` Jean-Christophe Helary
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=878tjxx1m4.fsf@jane \
--to=mbork@mbork.pl \
--cc=emacs-devel@gnu.org \
--cc=jean.christophe.helary@gmail.com \
--cc=npostavs@users.sourceforge.net \
/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).