[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Edebug: not stopping at a function's start. Documentation amendment.

From: Alan Mackenzie
Subject: Edebug: not stopping at a function's start. Documentation amendment.
Date: Mon, 21 Sep 2015 15:49:24 +0000
User-agent: Mutt/1.5.23 (2014-03-12)

Hello, Emacs.

In bug #21365, Paul Pogonyshev was asking for a feature in Edebug,
whereby execution would not stop at the beginning of an instrumented
function, only at a breakpoint.  I've been wanting this for several
years, too.

It turns out that the feature is already available by setting
`edebug-initial-mode', but is disguised by obscure documentation.  This
documentation describes how the feature is implemented rather than what
the user sees and must do.

I have rewritten the pertinent paragraph in edebug.texi as follows to
fix this, and also moved the paragraph a wee bit higher up.

Any objections to me committing this?

diff --git a/doc/lispref/edebug.texi b/doc/lispref/edebug.texi
index 9080bf7..e086be3 100644
--- a/doc/lispref/edebug.texi
+++ b/doc/lispref/edebug.texi
@@ -281,6 +281,15 @@ can still stop the program by typing @kbd{S}, or any 
editing command.
 In general, the execution modes earlier in the above list run the
 program more slowly or stop sooner than the modes later in the list.
+When you enter a new Edebug level, Edebug will normally stop at the
+first instrumented function it encounters.  If you prefer to stop only
+at a break point, or not at all (for example, when gathering coverage
+data), change the value of @code{edebug-initial-mode} from its default
address@hidden to @code{go} or @code{Go-nonstop}, or one of its other
+values (@pxref{Edebug Options}).  Note that you may reenter the same
+Edebug level several times if, for example, an instrumented function
+is called several times from one command.
 While executing or tracing, you can interrupt the execution by typing
 any Edebug command.  Edebug stops the program at the next stop point and
 then executes the command you typed.  For example, typing @kbd{t} during
@@ -300,13 +309,6 @@ executing a keyboard macro outside of Edebug does not 
affect commands
 inside Edebug.  This is usually an advantage.  See also the
 @code{edebug-continue-kbd-macro} option in @ref{Edebug Options}.
-When you enter a new Edebug level, the initial execution mode comes
-from the value of the variable @code{edebug-initial-mode}
-(@pxref{Edebug Options}).  By default, this specifies step mode.  Note
-that you may reenter the same Edebug level several times if, for
-example, an instrumented function is called several times from one
 @defopt edebug-sit-for-seconds
 This option specifies how many seconds to wait between execution steps
 in trace mode or continue mode.  The default is 1 second.

By the way, has anybody any idea why git diff is putting source text on
the same lines as the line numbers?  (I upgraded to git-2.4.9 very

Alan Mackenzie (Nuremberg, Germany).

reply via email to

[Prev in Thread] Current Thread [Next in Thread]