@c -*-texinfo-*-
@c This is part of the GNU Emacs Lisp Reference Manual.
@c Copyright (C) 1990, 1991, 1992, 1993, 1994, 1995, 1998, 1999
-@c Free Software Foundation, Inc.
+@c Free Software Foundation, Inc.
@c See the file elisp.texi for copying conditions.
@setfilename ../info/buffers
@node Buffers, Windows, Backups and Auto-Saving, Top
@code{insert-buffer-substring} copies the string from the original
current buffer to the specified (and now current) buffer.
- If the buffer appended to happens to be displayed in some window,
+ If the buffer appended to happens to be displayed in some window,
the next redisplay will show how its text has changed. Otherwise, you
will not see the change immediately on the screen. The buffer becomes
current temporarily during the execution of the command, but this does
@end defun
@defspec 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
-@var{body}. The current buffer is restored even in case of an abnormal
-exit via @code{throw} or error (@pxref{Nonlocal Exits}).
+The @code{save-current-buffer} special form 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 @var{body}. The current buffer is restored even in case of an
+abnormal exit via @code{throw} or error (@pxref{Nonlocal Exits}).
If the buffer that used to be current has been killed by the time of
exit from @code{save-current-buffer}, then it is not made current again,
Buffers that are ephemeral and generally uninteresting to the user
have names starting with a space, so that the @code{list-buffers} and
-@code{buffer-menu} commands don't mention them. A name starting with
+@code{buffer-menu} commands don't mention them (but if such a buffer
+visits a file, it @strong{is} mentioned). A name starting with
space also initially disables recording undo information; see
@ref{Undo}.
This function returns the buffer specified by @var{buffer-or-name}.
If @var{buffer-or-name} is a string and there is no buffer with that
name, the value is @code{nil}. If @var{buffer-or-name} is a buffer, it
-is returned as given; that is not very useful, so the argument is usually
+is returned as given; that is not very useful, so the argument is usually
a name. For example:
@example
@comment node-name, next, previous, up
@section Comparison of Modification Time
@cindex comparison of modification time
-@cindex modification time, comparison of
+@cindex modification time, comparison of
Suppose that you visit a file and make changes in its buffer, and
meanwhile the file itself is changed on disk. At this point, saving the
Depending on the user's answer, the function may return normally, in
which case the modification of the buffer proceeds, or it may signal a
@code{file-supersession} error with data @code{(@var{filename})}, in which
-case the proposed buffer modification is not allowed.
+case the proposed buffer modification is not allowed.
This function is called automatically by Emacs on the proper
occasions. It exists so you can customize Emacs by redefining it.
@cindex buffer, read-only
If a buffer is @dfn{read-only}, then you cannot change its contents,
-although you may change your view of the contents by scrolling and
+although you may change your view of the contents by scrolling and
narrowing.
Read-only buffers are used in two kinds of situations:
@cindex buffer list
The @dfn{buffer list} is a list of all live buffers. Creating a
-buffer adds it to this list, and killing a buffer excises it. The order
-of the buffers in the list is based primarily on how recently each
-buffer has been displayed in the selected window. Buffers move to the
-front of the list when they are selected and to the end when they are
-buried (see @code{bury-buffer}, below). Several functions, notably
-@code{other-buffer}, use this ordering. A buffer list displayed for the
-user also follows this order.
+buffer adds it to this list, and killing a buffer removes it. The
+order of the buffers in the list is based primarily on how recently
+each buffer has been displayed in the selected window. Buffers move
+to the front of the list when they are selected (selecting a window
+that already displays the buffer counts as selecting the buffer), and
+to the end when they are buried (see @code{bury-buffer}, below).
+Several functions, notably @code{other-buffer}, use this ordering. A
+buffer list displayed for the user also follows this order.
In addition to the fundamental Emacs buffer list, each frame has its
own version of the buffer list, in which the buffers that have been
;; @r{Note that the name of the minibuffer}
;; @r{begins with a space!}
(mapcar (function buffer-name) (buffer-list))
- @result{} ("buffers.texi" " *Minibuf-1*"
+ @result{} ("buffers.texi" " *Minibuf-1*"
"buffer.c" "*Help*" "TAGS")
@end group
@end example
Any processes that have this buffer as the @code{process-buffer} are
sent the @code{SIGHUP} signal, which normally causes them to terminate.
(The basic meaning of @code{SIGHUP} is that a dialup line has been
-disconnected.) @xref{Deleting Processes}.
+disconnected.) @xref{Signals to Processes}.
If the buffer is visiting a file and contains unsaved changes,
@code{kill-buffer} asks the user to confirm before the buffer is killed.
This creates an indirect buffer named @var{name} whose base buffer
is @var{base-buffer}. The argument @var{base-buffer} may be a buffer
or a string.
-
+
If @var{base-buffer} is an indirect buffer, its base buffer is used as
the base for the new buffer.
@end deffn