Mercurial > emacs
comparison man/building.texi @ 72811:89ca8074ddae
(Compilation Mode): Clarification.
(Grep Searching): Add xref to Compilation Mode.
author | Richard M. Stallman <rms@gnu.org> |
---|---|
date | Mon, 11 Sep 2006 17:15:34 +0000 |
parents | a085a4e8fd54 |
children | c1e1c7527b1a a1a25ac6c88a |
comparison
equal
deleted
inserted
replaced
72810:709ee6c1e02a | 72811:89ca8074ddae |
---|---|
208 To parse the compiler error messages sequentially, type @kbd{C-x `} | 208 To parse the compiler error messages sequentially, type @kbd{C-x `} |
209 (@code{next-error}). The character following the @kbd{C-x} is the | 209 (@code{next-error}). The character following the @kbd{C-x} is the |
210 backquote or ``grave accent,'' not the single-quote. This command is | 210 backquote or ``grave accent,'' not the single-quote. This command is |
211 available in all buffers, not just in @samp{*compilation*}; it | 211 available in all buffers, not just in @samp{*compilation*}; it |
212 displays the next error message at the top of one window and source | 212 displays the next error message at the top of one window and source |
213 location of the error in another window. It also momentarily | 213 location of the error in another window. It also temporarily |
214 highlights the relevant source line. You can change the behavior of | 214 highlights the relevant source line, for a period controlled by the |
215 this highlighting with the variable @code{next-error-highlight}. | 215 variable @code{next-error-highlight}. |
216 | 216 |
217 The first time @w{@kbd{C-x `}} is used after the start of a compilation, | 217 The first time @w{@kbd{C-x `}} is used after the start of a compilation, |
218 it moves to the first error's location. Subsequent uses of @kbd{C-x | 218 it moves to the first error's location. Subsequent uses of @kbd{C-x |
219 `} advance down to subsequent errors. If you visit a specific error | 219 `} advance down to subsequent errors. If you visit a specific error |
220 message with @key{RET} or @kbd{Mouse-2}, subsequent @w{@kbd{C-x `}} | 220 message with @key{RET} or @kbd{Mouse-2}, subsequent @w{@kbd{C-x `}} |
333 | 333 |
334 @node Grep Searching | 334 @node Grep Searching |
335 @section Searching with Grep under Emacs | 335 @section Searching with Grep under Emacs |
336 | 336 |
337 Just as you can run a compiler from Emacs and then visit the lines | 337 Just as you can run a compiler from Emacs and then visit the lines |
338 with compilation errors, you can also run @code{grep} and | 338 with compilation errors, you can also run @code{grep} and then visit |
339 then visit the lines on which matches were found. This works by | 339 the lines on which matches were found. This works by treating the |
340 treating the matches reported by @code{grep} as if they were ``errors.'' | 340 matches reported by @code{grep} as if they were ``errors.'' The |
341 buffer of matches uses Grep mode, which is a variant of Compilation | |
342 mode (@pxref{Compilation Mode}). | |
341 | 343 |
342 @table @kbd | 344 @table @kbd |
343 @item M-x grep | 345 @item M-x grep |
344 @item M-x lgrep | 346 @item M-x lgrep |
345 Run @code{grep} asynchronously under Emacs, with matching lines | 347 Run @code{grep} asynchronously under Emacs, with matching lines |