[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Emacs-diffs] emacs-25 7c1e598: Document `byte-compile-debug' in the ELi
From: |
Philipp Stephani |
Subject: |
[Emacs-diffs] emacs-25 7c1e598: Document `byte-compile-debug' in the ELisp manual |
Date: |
Tue, 31 Jan 2017 20:10:55 +0000 (UTC) |
branch: emacs-25
commit 7c1e598a0559db79a5166e34514413e3f524eeff
Author: Philipp Stephani <address@hidden>
Commit: Philipp Stephani <address@hidden>
Document `byte-compile-debug' in the ELisp manual
* doc/lispref/compile.texi: Document variable `byte-compile-debug'.
---
doc/lispref/compile.texi | 9 ++++++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/doc/lispref/compile.texi b/doc/lispref/compile.texi
index b1cc04b..441ee9a 100644
--- 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.
address@hidden 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
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Emacs-diffs] emacs-25 7c1e598: Document `byte-compile-debug' in the ELisp manual,
Philipp Stephani <=