diff options
author | Richard M. Stallman <rms@gnu.org> | 1998-05-19 03:45:57 +0000 |
---|---|---|
committer | Richard M. Stallman <rms@gnu.org> | 1998-05-19 03:45:57 +0000 |
commit | a9f0a989a17f47f9d25b7a426b4e82a8ff684ee4 (patch) | |
tree | d62b5592064177c684f1509989b223623db3f24c /lispref/buffers.texi | |
parent | c6d6572475603083762cb0155ae966de7710bb9c (diff) | |
download | emacs-a9f0a989a17f47f9d25b7a426b4e82a8ff684ee4.tar.gz |
*** empty log message ***
Diffstat (limited to 'lispref/buffers.texi')
-rw-r--r-- | lispref/buffers.texi | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/lispref/buffers.texi b/lispref/buffers.texi index 600ff3e54b5..c54f1e6b9b0 100644 --- a/lispref/buffers.texi +++ b/lispref/buffers.texi @@ -47,9 +47,9 @@ not be displayed in any windows. Buffers in Emacs editing are objects that have distinct names and hold text that can be edited. Buffers appear to Lisp programs as a special -data type. You can think of the contents of a buffer as an extendable -string; insertions and deletions may occur in any part of the buffer. -@xref{Text}. +data type. You can think of the contents of a buffer as a string that +you can extend; insertions and deletions may occur in any part of the +buffer. @xref{Text}. A Lisp buffer object contains numerous pieces of information. Some of this information is directly accessible to the programmer through @@ -112,7 +112,7 @@ the subroutine does not change which buffer is current (unless, of course, that is the subroutine's purpose). Therefore, you should normally use @code{set-buffer} within a @code{save-current-buffer} or @code{save-excursion} (@pxref{Excursions}) form that will restore the -current buffer when your function is done . Here is an example, the +current buffer when your function is done. Here is an example, the code for the command @code{append-to-buffer} (with the documentation string abridged): @@ -201,8 +201,8 @@ An error is signaled if @var{buffer-or-name} does not identify an existing buffer. @end defun +@defspec save-current-buffer body... @tindex save-current-buffer -@defmac save-current-buffer body... The @code{save-current-buffer} macro saves the identity of the current buffer, evaluates the @var{body} forms, and finally restores that buffer as current. The return value is the value of the last form in @@ -215,8 +215,8 @@ of course. Instead, whichever buffer was current just before exit remains current. @end defmac -@tindex with-current-buffer @defmac with-current-buffer buffer body... +@tindex with-current-buffer The @code{with-current-buffer} macro saves the identity of the current buffer, makes @var{buffer} current, evaluates the @var{body} forms, and finally restores the buffer. The return value is the value of the last @@ -224,8 +224,8 @@ form in @var{body}. The current buffer is restored even in case of an abnormal exit via @code{throw} or error (@pxref{Nonlocal Exits}). @end defmac -@tindex with-temp-buffer @defmac with-temp-buffer body... +@tindex with-temp-buffer The @code{with-temp-buffer} macro evaluates the @var{body} forms with a temporary buffer as the current buffer. It saves the identity of the current buffer, creates a temporary buffer and makes it current, |