# HG changeset patch # User Richard M. Stallman # Date 1058198444 0 # Node ID d51ac8d52e63f39d490fdf9d624968cf1a4482ec # Parent 9fbd3ef3087defb0914155295afce4c8c948377e (Byte Compilation): Explain no-byte-compile (Compiler Errors): New node. diff -r 9fbd3ef3087d -r d51ac8d52e63 lispref/compile.texi --- a/lispref/compile.texi Mon Jul 14 15:59:52 2003 +0000 +++ b/lispref/compile.texi Mon Jul 14 16:00:44 2003 +0000 @@ -39,6 +39,14 @@ not work in subsequent versions if they contain character constants with modifier bits. +@vindex no-byte-compile + If you do not want a Lisp file to be compiled, ever, put a file-local +variable binding for @code{no-byte-compile} into it, like this: + +@example +;; -*-no-byte-compile: t; -*- +@end example + @xref{Compilation Errors}, for how to investigate errors occurring in byte compilation. @@ -48,6 +56,7 @@ * Docs and Compilation:: Dynamic loading of documentation strings. * Dynamic Loading:: Dynamic loading of individual functions. * Eval During Compile:: Code to be evaluated when you compile. +* Compiler Errors:: Handling compiler error messages. * Byte-Code Objects:: The data type used for byte-compiled functions. * Disassembly:: Disassembling byte-code; how to read byte-code. @end menu @@ -397,6 +406,21 @@ to what @code{eval-when-compile} does. @end defspec +@node Compiler Errors +@section Compiler Errors +@cindex compiler errors + + Byte compilation writes errors and warnings into the buffer +@samp{*Compile-Log*}. The messages include file names and line +numbers that identify the location of the problem. The usual Emacs +commands for operating on compiler diagnostics work properly on +these messages. + + However, the warnings about functions that were used but not +defined are always ``located'' at the end of the file, so these +commands won't find the places they are really used. To do that, +you must search for the function names. + @node Byte-Code Objects @section Byte-Code Function Objects @cindex compiled function