all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Noam Postavsky <npostavs@users.sourceforge.net>
To: Marcin Borkowski <mbork@mbork.pl>
Cc: Jean-Christophe Helary <jean.christophe.helary@gmail.com>,
	Emacs-Devel devel <emacs-devel@gnu.org>
Subject: Re: debugging elisp ?
Date: Sun, 9 Jul 2017 08:13:02 -0400	[thread overview]
Message-ID: <CAM-tV-_cSNH3Uq4eWU9ttDZ8o7So0uiBCdSNjz6z8GuTNVWLrA@mail.gmail.com> (raw)
In-Reply-To: <878tjxx1m4.fsf@jane>

On Sun, Jul 9, 2017 at 7:59 AM, Marcin Borkowski <mbork@mbork.pl> wrote:
>
> Won't
> M-x edebug-all-defuns
> and then
> M-x eval-buffer
> in package.el work as well (and be easier)?

Oh, yes, good point. I usually mark only some functions with
edebug-instrument-function in a dolist loop, so I didn't think of the
more straightforward way.

On Sun, Jul 9, 2017 at 7:58 AM, Jean-Christophe Helary
<jean.christophe.helary@gmail.com> wrote:
>
> So there is no way I can run package without marking all the functions for debugging?

You can run package without marking it, but you can't step with edebug
through a function without without instrumenting it first. You can
instrument other functions while debugging if you see something
interesting, see (elisp) Instrumenting.



  reply	other threads:[~2017-07-09 12:13 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
2017-07-09 12:13         ` Noam Postavsky [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAM-tV-_cSNH3Uq4eWU9ttDZ8o7So0uiBCdSNjz6z8GuTNVWLrA@mail.gmail.com \
    --to=npostavs@users.sourceforge.net \
    --cc=emacs-devel@gnu.org \
    --cc=jean.christophe.helary@gmail.com \
    --cc=mbork@mbork.pl \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.