From 66c466d4fdb7f874f19191ca06fad92f9c2393cd Mon Sep 17 00:00:00 2001 From: Martin Rudalics Date: Sun, 18 Nov 2012 12:34:36 +0100 Subject: [PATCH] Fix example for Display Action Functions. * windows.texi (Display Action Functions): Fix recently added example. Suggested by Michael Heerdegen. --- doc/lispref/ChangeLog | 5 +++++ doc/lispref/windows.texi | 3 ++- 2 files changed, 7 insertions(+), 1 deletion(-) diff --git a/doc/lispref/ChangeLog b/doc/lispref/ChangeLog index 389d94bf8c5..bdf4ef13488 100644 --- a/doc/lispref/ChangeLog +++ b/doc/lispref/ChangeLog @@ -1,3 +1,8 @@ +2012-11-18 Martin Rudalics + + * windows.texi (Display Action Functions): Fix recently added + example. Suggested by Michael Heerdegen. + 2012-11-18 Paul Eggert Minor cleanup for times as lists of four integers. diff --git a/doc/lispref/windows.texi b/doc/lispref/windows.texi index 439e807260f..46b31ef0d9f 100644 --- 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 -- 2.39.2