summaryrefslogtreecommitdiff
path: root/lispref/compile.texi
diff options
context:
space:
mode:
authorRichard M. Stallman <rms@gnu.org>1996-12-20 00:09:23 +0000
committerRichard M. Stallman <rms@gnu.org>1996-12-20 00:09:23 +0000
commit3607fb8575ea1d18cd5ea01e2bb629c1d4d3adfd (patch)
tree38bb04b52ca7540b895803764544f83feea318ce /lispref/compile.texi
parent9226239027548f76d2c21b94fb997df71e829967 (diff)
downloademacs-3607fb8575ea1d18cd5ea01e2bb629c1d4d3adfd.tar.gz
Minor cleanups for overfull hboxes.
Diffstat (limited to 'lispref/compile.texi')
-rw-r--r--lispref/compile.texi6
1 files changed, 3 insertions, 3 deletions
diff --git a/lispref/compile.texi b/lispref/compile.texi
index c085634c39b..d43ea51f074 100644
--- a/lispref/compile.texi
+++ b/lispref/compile.texi
@@ -94,9 +94,9 @@ the @code{byte-compile} function. You can compile a whole file with
@code{byte-compile-file}, or several files with
@code{byte-recompile-directory} or @code{batch-byte-compile}.
- When you run the byte compiler, you may get warnings in a buffer
-called @samp{*Compile-Log*}. These report things in your program that
-suggest a problem but are not necessarily erroneous.
+ The byte compiler produces error messages and warnings about each file
+in a buffer called @samp{*Compile-Log*}. These report things in your
+program that suggest a problem but are not necessarily erroneous.
@cindex macro compilation
Be careful when byte-compiling code that uses macros. Macro calls are