[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Emacs-diffs] Changes to emacs/lisp/emacs-lisp/edebug.el
From: |
Richard M. Stallman |
Subject: |
[Emacs-diffs] Changes to emacs/lisp/emacs-lisp/edebug.el |
Date: |
Tue, 20 Aug 2002 13:27:37 -0400 |
Index: emacs/lisp/emacs-lisp/edebug.el
diff -c emacs/lisp/emacs-lisp/edebug.el:3.54
emacs/lisp/emacs-lisp/edebug.el:3.55
*** emacs/lisp/emacs-lisp/edebug.el:3.54 Sun Jul 28 21:51:09 2002
--- emacs/lisp/emacs-lisp/edebug.el Fri Aug 2 14:00:18 2002
***************
*** 531,542 ****
;;;###autoload
(defun edebug-eval-top-level-form ()
! "Evaluate a top level form, such as a defun or defmacro.
! This is like `eval-defun', but the code is always instrumented for Edebug.
! Print its name in the minibuffer and leave point where it is,
! or if an error occurs, leave point after it with mark at the original point."
(interactive)
! (eval
;; Bind edebug-all-forms only while reading, not while evalling
;; but this causes problems while edebugging edebug.
(let ((edebug-all-forms t)
--- 531,554 ----
;;;###autoload
(defun edebug-eval-top-level-form ()
! "Evaluate the top level form point is in, stepping through with Edebug.
! This is like `eval-defun' except that it steps the code for Edebug
! before evaluating it. It displays the value in the echo area
! using `eval-expression' (which see).
!
! If you do this on a function definition
! such as a defun or defmacro, it defines the function and instruments
! its definition for Edebug, so it will do Edebug stepping when called
! later. It displays `Edebug: FUNCTION' in the echo area to indicate
! that FUNCTION is now instrumented for Edebug.
!
! If the current defun is actually a call to `defvar' or `defcustom',
! evaluating it this way resets the variable using its initial value
! expression even if the variable already has some other value.
! \(Normally `defvar' and `defcustom' do not alter the value if there
! already is one.)"
(interactive)
! (eval-expression
;; Bind edebug-all-forms only while reading, not while evalling
;; but this causes problems while edebugging edebug.
(let ((edebug-all-forms t)