Luc Teirlinck <[EMAIL PROTECTED]> writes:
> Lute Kamstra wrote:
>
>I think your formulation is a bit misleading. Emacs' debugger can't
>step through a primitive, gdb can.
>
> So what about:
[...]
> ! type @kbd{C-M-x} on its definition.) You can not use the Lisp debugger
> ! to step thr
Lute Kamstra wrote:
I think your formulation is a bit misleading. Emacs' debugger can't
step through a primitive, gdb can.
So what about:
===File ~/debugging.texi-diff===
*** debugging.texi 14 Jun 2005 08:19:54 -0500 1.32
--- debugging.te
Luc Teirlinck <[EMAIL PROTECTED]> writes:
> What about the following additional change to debugging.texi? It may
> not be that surprising that if you can not step through a
> byte-compiled function, you can not step through a primitive function
> either, but it may not hurt to
What about the following additional change to debugging.texi? It may
not be that surprising that if you can not step through a
byte-compiled function, you can not step through a primitive function
either, but it may not hurt to explicitly mention it.
I can install if desired.
===File
Luc Teirlinck <[EMAIL PROTECTED]> writes:
> What about the following additional change:
I like it,
Lute.
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
What about the following additional change:
===File ~/debug.el-diff=
*** debug.el11 Jun 2005 18:36:43 -0500 1.84
--- debug.el11 Jun 2005 19:22:48 -0500
***
*** 698,706
To specify a nil argument interactively, exit with an em
(defun debug-on-entry (function)
"Request FUNCTION to invoke debugger each time it is called.
+ When called interactively, prompt for FUNCTION in the minibuffer.
That is useful to add.
If you tell the debugger to continue, FUNCTION's execution proceeds.
This works by
I think the empty string argument is a kludge. Maybe we should just
not document it and tell people to use a symbol or nil from lisp and
the name of the function or no name (i.e., the empty string)
interactively.
I agree. It is a mistake to try to document every detail of the
beh
@var{function-name} in the minibuffer. If @var{function-name} is
! omitted, @code{nil} or the empty string, it cancels break-on-entry
for all
You need a comment after @code{nil} to eliminate a misreading. With
that change, please install.
Correction--you need a comma
Luc Teirlinck <[EMAIL PROTECTED]> writes:
> Richard Stallman wrote:
>
>@var{function-name} in the minibuffer. If @var{function-name} is
>! omitted, @code{nil} or the empty string, it cancels break-on-entry
> for all
>
>You need a comment after @code{nil} to eliminate a misrea
those is included as well.
I can install the patches if desired.
===File ~/debugging.texi-diff===
*** debugging.texi 10 Jun 2005 20:55:09 -0500 1.30
--- debugging.texi 10 Jun 2005 21:40:18 -0500
***
*** 271,282
This function undoes
@var{function-name} in the minibuffer. If @var{function-name} is
! omitted, @code{nil} or the empty string, it cancels break-on-entry for all
You need a comment after @code{nil} to eliminate a misreading. With
that change, please install.
_
I propose the following changes to debugging.texi. The current doc of
eval-expression-debug-on-error gives the impression that the
default value is nil, whereas it is t.
I can install if desired.
===File ~/debugging.texi-diff===
*** debugging.texi 05 Mar 2005 12
I've updated lispref/debugging.texi. Shall I commit my changes?
Lute.
2005-02-28 Lute Kamstra <[EMAIL PROTECTED]>
* debugging.texi (Debugging): Fix typo.
(Error Debugging): Document eval-expression-debug-on-error.
(Function Debugging): Update example.
14 matches
Mail list logo
