summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorXue Fuqiao <xfq.free@gmail.com>2015-08-23 19:21:33 +0800
committerXue Fuqiao <xfq.free@gmail.com>2015-08-23 19:21:33 +0800
commitef00774df4582592ac675fbe803ecc887e0e248a (patch)
tree48cace2952bfdd6ab001c15717f38a50c4ca8928
parent2f0d41ea4fd47bbc53a53d7634869b21cf03c1a0 (diff)
downloademacs-ef00774df4582592ac675fbe803ecc887e0e248a.tar.gz
* doc/lispintro/emacs-lisp-intro.texi (Switching Buffers): Clarify
"invisible window".
-rw-r--r--doc/lispintro/emacs-lisp-intro.texi8
1 files 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