[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Emacs-diffs] Changes to emacs/man/building.texi
From: |
Richard M . Stallman |
Subject: |
[Emacs-diffs] Changes to emacs/man/building.texi |
Date: |
Sun, 16 Oct 2005 22:34:50 -0400 |
Index: emacs/man/building.texi
diff -c emacs/man/building.texi:1.72 emacs/man/building.texi:1.73
*** emacs/man/building.texi:1.72 Mon Oct 10 12:27:21 2005
--- emacs/man/building.texi Mon Oct 17 02:34:49 2005
***************
*** 63,79 ****
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}).
Starting a compilation displays the buffer @samp{*compilation*} in
another window but does not select it. The buffer's mode line tells
--- 63,78 ----
directory.
@vindex compile-command
! 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
***************
*** 231,236 ****
--- 230,243 ----
if the current buffer can be the target of @code{next-error}, it is
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.
- [Emacs-diffs] Changes to emacs/man/building.texi, Nick Roberts, 2005/10/06
- [Emacs-diffs] Changes to emacs/man/building.texi, Nick Roberts, 2005/10/10
- [Emacs-diffs] Changes to emacs/man/building.texi,
Richard M . Stallman <=
- [Emacs-diffs] Changes to emacs/man/building.texi, Nick Roberts, 2005/10/17
- [Emacs-diffs] Changes to emacs/man/building.texi, Nick Roberts, 2005/10/24
- [Emacs-diffs] Changes to emacs/man/building.texi, Nick Roberts, 2005/10/30
- [Emacs-diffs] Changes to emacs/man/building.texi, Nick Roberts, 2005/10/31