# HG changeset patch # User Thien-Thi Nguyen # Date 1152086005 0 # Node ID 6e10c3f1b820eec1b434dedbc20a4508b11a7c53 # Parent fbe329a11ceeb0914f2c6d5aad8d2d51f13f5fe6 (Lisp Eval): Througout, replace eval-current-buffer with eval-buffer. diff -r fbe329a11cee -r 6e10c3f1b820 man/building.texi --- a/man/building.texi Wed Jul 05 07:47:41 2006 +0000 +++ b/man/building.texi Wed Jul 05 07:53:25 2006 +0000 @@ -1250,7 +1250,7 @@ the echo area (@code{eval-defun}). @item M-x eval-region Evaluate all the Lisp expressions in the region. -@item M-x eval-current-buffer +@item M-x eval-buffer Evaluate all the Lisp expressions in the buffer. @end table @@ -1305,11 +1305,11 @@ definition for Edebug (@pxref{Instrumenting, Instrumenting for Edebug,, elisp, the Emacs Lisp Reference Manual}). @findex eval-region -@findex eval-current-buffer +@findex eval-buffer The most general command for evaluating Lisp expressions from a buffer is @code{eval-region}. @kbd{M-x eval-region} parses the text of the region as one or more Lisp expressions, evaluating them one by one. -@kbd{M-x eval-current-buffer} is similar but evaluates the entire +@kbd{M-x eval-buffer} is similar but evaluates the entire buffer. This is a reasonable way to install the contents of a file of Lisp code that you are ready to test. Later, as you find bugs and change individual functions, use @kbd{C-M-x} on each function that you