Document `byte-compile-debug' in the ELisp manual

* doc/lispref/compile.texi: Document variable `byte-compile-debug'.

diff --git a/doc/lispref/compile.texi b/doc/lispref/compile.texi
index b1cc04be09d314446df920a7b99bb7a5dc7bc6bf..441ee9afb262ebf8853cbf2414a47447014d287c 100644 (file)
--- a/doc/lispref/compile.texi
+++ b/doc/lispref/compile.texi
@@ -89,9 +89,12 @@ the @code{byte-compile} function.  You can compile a whole file with
 @code{byte-recompile-directory} or @code{batch-byte-compile}.
 
   Sometimes, the byte compiler produces warning and/or error messages
-(@pxref{Compiler Errors}, for details).  These messages are recorded
-in a buffer called @file{*Compile-Log*}, which uses Compilation mode.
-@xref{Compilation Mode,,,emacs, The GNU Emacs Manual}.
+(@pxref{Compiler Errors}, for details).  These messages are normally
+recorded in a buffer called @file{*Compile-Log*}, which uses
+Compilation mode.  @xref{Compilation Mode,,,emacs, The GNU Emacs
+Manual}.  However, if the variable @code{byte-compile-debug} is
+non-nil, error message will be signaled as Lisp errors instead
+(@pxref{Errors}).
 
 @cindex macro compilation
   Be careful when writing macro calls in files that you intend to