[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: debugging elisp ?
From: |
Noam Postavsky |
Subject: |
Re: debugging elisp ? |
Date: |
Sun, 9 Jul 2017 07:48:44 -0400 |
On Sun, Jul 9, 2017 at 6:49 AM, Jean-Christophe Helary
<address@hidden> 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)))
- debugging elisp ?, Jean-Christophe Helary, 2017/07/09
- Re: debugging elisp ?, Marcin Borkowski, 2017/07/09
- Re: debugging elisp ?, Jean-Christophe Helary, 2017/07/09
- Re: debugging elisp ?,
Noam Postavsky <=
- Re: debugging elisp ?, Jean-Christophe Helary, 2017/07/09
- Re: debugging elisp ?, Marcin Borkowski, 2017/07/09
- Re: debugging elisp ?, Noam Postavsky, 2017/07/09
- Re: debugging elisp ?, Jean-Christophe Helary, 2017/07/09
- Re: debugging elisp ?, Michael Heerdegen, 2017/07/10
- Re: debugging elisp ?, Jean-Christophe Helary, 2017/07/10