From ef00774df4582592ac675fbe803ecc887e0e248a Mon Sep 17 00:00:00 2001 From: Xue Fuqiao Date: Sun, 23 Aug 2015 19:21:33 +0800 Subject: [PATCH] * doc/lispintro/emacs-lisp-intro.texi (Switching Buffers): Clarify "invisible window". --- doc/lispintro/emacs-lisp-intro.texi | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/lispintro/emacs-lisp-intro.texi b/doc/lispintro/emacs-lisp-intro.texi index 183e68f6660..a9f02f5e848 100644 --- a/doc/lispintro/emacs-lisp-intro.texi +++ b/doc/lispintro/emacs-lisp-intro.texi @@ -2840,10 +2840,10 @@ following more complex expression: @c noindent In this case, the first argument to @code{other-buffer} tells it which buffer to skip---the current one---and the second argument tells -@code{other-buffer} it is OK to switch to a visible buffer. -In regular use, @code{switch-to-buffer} takes you to an invisible -window since you would most likely use @kbd{C-x o} (@code{other-window}) -to go to another visible buffer.} +@code{other-buffer} it is OK to switch to a visible buffer. In +regular use, @code{switch-to-buffer} takes you to a buffer not visible +in windows since you would most likely use @kbd{C-x o} +(@code{other-window}) to go to another visible buffer.} In the programming examples in later sections of this document, you will see the function @code{set-buffer} more often than -- 2.11.4.GIT