# HG changeset patch
# User Martin Rudalics <rudalics@gmx.at>
# Date 1224691675 0
# Node ID 26ffccc147703366b22c3afe906081a9a851fcda
# Parent  90d78f7a7eba6d352639dffc3fe87a0f119b8457
(Killing Buffers): Update documentation of kill-buffer.

diff -r 90d78f7a7eba -r 26ffccc14770 doc/lispref/buffers.texi
--- a/doc/lispref/buffers.texi	Wed Oct 22 15:35:00 2008 +0000
+++ b/doc/lispref/buffers.texi	Wed Oct 22 16:07:55 2008 +0000
@@ -996,10 +996,11 @@
 @end group
 @end example
 
-@deffn Command kill-buffer buffer-or-name
+@deffn Command kill-buffer &optional buffer-or-name
 This function kills the buffer @var{buffer-or-name}, freeing all its
 memory for other uses or to be returned to the operating system.  If
-@var{buffer-or-name} is @code{nil}, it kills the current buffer.
+@var{buffer-or-name} is @code{nil} or omitted, it kills the current
+buffer.
 
 Any processes that have this buffer as the @code{process-buffer} are
 sent the @code{SIGHUP} signal, which normally causes them to terminate.
@@ -1012,6 +1013,9 @@
 for confirmation, clear the modified flag before calling
 @code{kill-buffer}.  @xref{Buffer Modification}.
 
+This function calls `replace-buffer-in-windows' for cleaning up all
+windows currently displaying the buffer to be killed.
+
 Killing a buffer that is already dead has no effect.
 
 This function returns @code{t} if it actually killed the buffer.  It