# HG changeset patch
# User Chong Yidong <cyd@stupidchicken.com>
# Date 1295061038 18000
# Node ID 4e6ae7191e28de04ad2e3b8c0f552152826f1c08
# Parent  bee0a8fef127b76ad747f7d72851512f79d8540d
* building.texi (Compilation): Improve instructions for running two compilations (Bug#7573).

diff -r bee0a8fef127 -r 4e6ae7191e28 doc/emacs/ChangeLog
--- a/doc/emacs/ChangeLog	Fri Jan 14 21:55:58 2011 -0500
+++ b/doc/emacs/ChangeLog	Fri Jan 14 22:10:38 2011 -0500
@@ -1,5 +1,8 @@
 2011-01-15  Chong Yidong  <cyd@stupidchicken.com>
 
+	* building.texi (Compilation): Improve instructions for running two
+	compilations (Bug#7573).
+
 	* files.texi (Backup Names): Document the new location of the
 	last-resort backup file.
 
diff -r bee0a8fef127 -r 4e6ae7191e28 doc/emacs/building.texi
--- a/doc/emacs/building.texi	Fri Jan 14 21:55:58 2011 -0500
+++ b/doc/emacs/building.texi	Fri Jan 14 22:10:38 2011 -0500
@@ -122,10 +122,10 @@
 You can also kill the compilation process with @kbd{M-x
 kill-compilation}.
 
-  If you want to run two compilations at once, you should start the
-first one, then rename the @samp{*compilation*} buffer (perhaps using
-@code{rename-uniquely}; @pxref{Misc Buffer}), and start the other
-compilation.  That will create a new @samp{*compilation*} buffer.
+  To run two compilations at once, start the first one, then rename
+the @samp{*compilation*} buffer (perhaps using @code{rename-uniquely};
+@pxref{Misc Buffer}), then switch buffers and start the other
+compilation.  This will create a new @samp{*compilation*} buffer.
 
   Emacs does not expect a compiler process to launch asynchronous
 subprocesses; if it does, and they keep running after the main