[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: debugging elisp ?
From: |
Marcin Borkowski |
Subject: |
Re: debugging elisp ? |
Date: |
Sun, 09 Jul 2017 13:59:15 +0200 |
User-agent: |
mu4e 0.9.19; emacs 26.0.50 |
On 2017-07-09, at 13:48, Noam Postavsky <address@hidden> wrote:
> 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)))
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
- 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, 2017/07/09
- Re: debugging elisp ?, Jean-Christophe Helary, 2017/07/09
- Re: debugging elisp ?,
Marcin Borkowski <=
- 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