# HG changeset patch
# User Juri Linkov <juri@jurta.org>
# Date 1094117795 0
# Node ID 875c4c833a38213a292824044d3d6ed3e3d32906
# Parent  f259838f84128d3e4d27dfe6fd3176afbf11aae0
(Compilation Mode): Add a paragraph about rules
for finding the compilation buffer for `next-error'.

diff -r f259838f8412 -r 875c4c833a38 man/building.texi
--- a/man/building.texi	Thu Sep 02 09:30:26 2004 +0000
+++ b/man/building.texi	Thu Sep 02 09:36:35 2004 +0000
@@ -204,6 +204,14 @@
 buffer and finds no more error messages to visit, it fails and signals
 an Emacs error.
 
+  You don't have to be in the compilation buffer in order to use
+@code{next-error}.  If one window on the selected frame can be the
+target of the @code{next-error} call, it is used.  Else, if a buffer
+previously had @code{next-error} called on it, it is used.  Else,
+if the current buffer can be the target of @code{next-error}, it is
+used.  Else, all the buffers Emacs manages are tried for
+@code{next-error} support.
+
   @kbd{C-u C-x `} starts scanning from the beginning of the compilation
 buffer.  This is one way to process the same set of errors again.