Mercurial > emacs
changeset 66133:3e340cd42f9f
(Compilation Mode, Compilation): Clarified.
| author | Richard M. Stallman <rms@gnu.org> |
|---|---|
| date | Mon, 17 Oct 2005 02:34:49 +0000 |
| parents | 3fe20f1edf7b |
| children | b4d414f000c1 |
| files | man/building.texi |
| diffstat | 1 files changed, 18 insertions(+), 11 deletions(-) [+] |
line wrap: on
line diff
--- a/man/building.texi Sun Oct 16 23:46:15 2005 +0000 +++ b/man/building.texi Mon Oct 17 02:34:49 2005 +0000 @@ -63,17 +63,16 @@ directory. @vindex compile-command - When the shell command line is read, the minibuffer appears -containing a default command line, which is the command you used the -last time you did @kbd{M-x compile}. If you type just @key{RET}, the -same command line is used again. For the first @kbd{M-x compile}, the -default is @samp{make -k}, which is correct most of the time for -nontrivial programs. (@xref{Top,, Make, make, GNU Make Manual}.) -The default compilation command comes from the variable -@code{compile-command}; if the appropriate compilation command for a -file is something other than @samp{make -k}, it can be useful for the -file to specify a local value for @code{compile-command} (@pxref{File -Variables}). + The default for the compilation command is normally @samp{make -k}, +which is correct most of the time for nontrivial programs. +(@xref{Top,, Make, make, GNU Make Manual}.) If you have done @kbd{M-x +compile} before, the default each time is the command you used the +previous time. @code{compile} stores this command in the variable +@code{compile-command}, so setting that variable specifies the default +for the next use of @kbd{M-x compile}. If a file specifies a file +local value for @code{compile-command}, that provides the default when +you type @kbd{M-x compile} in that file's buffer. @xref{File +Variables}. Starting a compilation displays the buffer @samp{*compilation*} in another window but does not select it. The buffer's mode line tells @@ -232,6 +231,14 @@ used. Else, all the buffers Emacs manages are tried for @code{next-error} support. + If you're not in the compilation buffer when you run +@code{next-error}, Emacs will look for a buffer that contains error +messages. First, it looks for one displayed in the selected frame, +then for one that previously had @code{next-error} called on it, and +then at the current buffer. Finally, Emacs looks at all the remaining +buffers. @code{next-error} signals an error if it can't find any such +buffer. + @kbd{C-u C-x `} starts scanning from the beginning of the compilation buffer. This is one way to process the same set of errors again.