From 996d82f8278c9c82f7e5e1bf1ff09f401ea3204b Mon Sep 17 00:00:00 2001 From: "Richard M. Stallman" Date: Thu, 14 Mar 2002 09:00:46 +0000 Subject: [PATCH] Correct info on return values of switch-to-buffer and pop-to-buffer. --- lispref/windows.texi | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/lispref/windows.texi b/lispref/windows.texi index 8534ce6ca06..3d828f4db5e 100644 --- a/lispref/windows.texi +++ b/lispref/windows.texi @@ -768,7 +768,7 @@ List}. The @code{switch-to-buffer} function is often used interactively, as the binding of @kbd{C-x b}. It is also used frequently in programs. It -always returns @code{nil}. +returns the buffer that it switched to. @end deffn @deffn Command switch-to-buffer-other-window buffer-or-name &optional norecord @@ -791,7 +791,7 @@ unless @var{norecord} is non-@code{nil}. This function makes @var{buffer-or-name} the current buffer and switches to it in some window, preferably not the window previously selected. The ``popped-to'' window becomes the selected window within -its frame. +its frame. The return value is the buffer that was switched to. If the variable @code{pop-up-frames} is non-@code{nil}, @code{pop-to-buffer} looks for a window in any visible frame already -- 2.39.2