Fix example for Display Action Functions.

* windows.texi (Display Action Functions): Fix recently added
example.  Suggested by Michael Heerdegen.

diff --git a/doc/lispref/ChangeLog b/doc/lispref/ChangeLog
index 389d94bf8c565eadcb568a79509248ff2ebcd78b..bdf4ef13488046911910e9a260191f69bc379675 100644 (file)
--- a/doc/lispref/ChangeLog
+++ b/doc/lispref/ChangeLog
@@ -1,3 +1,8 @@
+2012-11-18  Martin Rudalics  <rudalics@gmx.at>
+
+       * windows.texi (Display Action Functions): Fix recently added
+       example.  Suggested by Michael Heerdegen.
+
 2012-11-18  Paul Eggert  <eggert@cs.ucla.edu>
 
        Minor cleanup for times as lists of four integers.

diff --git a/doc/lispref/windows.texi b/doc/lispref/windows.texi
index 439e807260f4a5347928c5becebba39a0a9258f8..46b31ef0d9f8464ff08d71c8b735528e7b3a1c94 100644 (file)
--- a/doc/lispref/windows.texi
+++ b/doc/lispref/windows.texi
@@ -2038,7 +2038,8 @@ Evaluating the form above will cause @code{display-buffer} to proceed as
 follows: If `*foo*' already appears on a visible or iconified frame, it
 will reuse its window.  Otherwise, it will try to pop up a new window
 or, if that is impossible, a new frame.  If all these steps fail, it
-will try to use some existing window.
+will proceed using whatever @code{display-buffer-base-action} and
+@code{display-buffer-fallback-action} prescribe.
 
    Furthermore, @code{display-buffer} will try to adjust a reused window
 (provided `*foo*' was put by @code{display-buffer} there before) or a