From d195726a7071d38a48acbeef9c307ebee3ca6ecc Mon Sep 17 00:00:00 2001 From: Chong Yidong Date: Sat, 22 Oct 2011 18:57:50 +0800 Subject: [PATCH] * doc/emacs/windows.texi (Displaying Buffers): Fix broken lispref link. --- doc/emacs/ChangeLog | 4 ++++ doc/emacs/windows.texi | 4 ++-- 2 files changed, 6 insertions(+), 2 deletions(-) diff --git a/doc/emacs/ChangeLog b/doc/emacs/ChangeLog index 06523d40d94..b90165cf55d 100644 --- a/doc/emacs/ChangeLog +++ b/doc/emacs/ChangeLog @@ -1,3 +1,7 @@ +2011-10-22 Chong Yidong + + * windows.texi (Displaying Buffers): Fix broken lispref link. + 2011-10-22 Chong Yidong * mini.texi (Minibuffer Exit): Rename from Strict Completion. diff --git a/doc/emacs/windows.texi b/doc/emacs/windows.texi index dc92e4a519c..600d0b07818 100644 --- a/doc/emacs/windows.texi +++ b/doc/emacs/windows.texi @@ -343,8 +343,8 @@ details. additionally select the displaying window so that you can begin editing its buffer. The command @kbd{C-x `} (@code{next-error}) is one example (@pxref{Compilation Mode}). Such commands work by calling -@code{pop-to-buffer} internally. @xref{Displaying Buffers,,Displaying -Buffers in Windows, elisp, The Emacs Lisp Reference Manual}. +@code{pop-to-buffer} internally. @xref{Switching Buffers,,Switching +to a Buffer in a Window, elisp, The Emacs Lisp Reference Manual}. Commands with names ending in @code{-other-window} behave like @code{display-buffer}, except that they never display in the selected -- 2.39.2