Re: debugging elisp ?

[Jean-Christophe Helary <jean.christophe.helary@gmail.com>]

I tried all the proposed solutions but I don't get what I'd like to have.

What I'd like to have is:

I run package in a window and in a different window I have all the variables/messages etc. appearing as I work inside package.

Maybe my "step by step" wording did not reflect what I really meant. Now that I see how it works, it is way too cumbersome for what I want to do, which is basically have a view on all the internal data as the package is run.

Jean-Christophe

> On Jul 9, 2017, at 20:59, Marcin Borkowski <mbork@mbork.pl> wrote:
> 
> 
> 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