the buffer, it remains fixed while more compilation output is added at
the end of the buffer.
+@cindex compilation buffer, keeping current position at the end
@vindex compilation-scroll-output
If you set the variable @code{compilation-scroll-output} to a
non-@code{nil} value, then the compilation buffer always scrolls to
mode, whose main feature is to provide a convenient way to look at the
source line where the error happened.
+ If you set the variable @code{compilation-scroll-output} to a
+non-@code{nil} value, then the compilation buffer always scrolls to
+follow output as it comes in.
+
@table @kbd
@item C-x `
Visit the locus of the next compiler error message or @code{grep} match.
GDB, which is free software, but you can also run DBX, SDB or XDB if you
have them. GUD can also serve as an interface to the Perl's debugging
mode, the Python debugger PDB, and to JDB, the Java Debugger.
+@xref{Debugger,, The Lisp Debugger, elisp, the Emacs Lisp Reference Manual},
+for information on debugging Emacs Lisp programs.
@menu
* Starting GUD:: How to start a debugger subprocess.
@vindex load-dangerous-libraries
@cindex Lisp files byte-compiled by XEmacs
- By default, Emacs refuses to load compiled Lisp files which weren't
-compiled with Emacs. This is because an incompatible change was
-introduced into XEmacs' byte compiler, which could produce files with
-byte codes that cause Emacs to crash. Set the variable
-@code{load-dangerous-libraries} to t if you want to change this
-behavior.
+ By default, Emacs refuses to load compiled Lisp files which were
+compiled with XEmacs, a modified versions of Emacs---they can cause
+Emacs to crash. Set the variable @code{load-dangerous-libraries} to
+@code{t} if you want to try loading them.
@node Lisp Eval
@section Evaluating Emacs-Lisp Expressions