/[emacs]/emacs/man/building.texi
ViewVC logotype

Diff of /emacs/man/building.texi

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 1.50 by nickrob, Wed Mar 23 03:06:01 2005 UTC revision 1.51 by rms, Mon Mar 28 21:04:39 2005 UTC
# Line 18  in the larger process of developing and Line 18  in the larger process of developing and
18  * Compilation Shell::   Customizing your shell properly  * Compilation Shell::   Customizing your shell properly
19                            for use in the compilation buffer.                            for use in the compilation buffer.
20  * Grep Searching::      Searching with grep.  * Grep Searching::      Searching with grep.
21    * Flymake::             Finding syntax errors on the fly.
22  * Debuggers::           Running symbolic debuggers for non-Lisp programs.  * Debuggers::           Running symbolic debuggers for non-Lisp programs.
23  * Executing Lisp::      Various modes for editing Lisp programs,  * Executing Lisp::      Various modes for editing Lisp programs,
24                            with different facilities for running                            with different facilities for running
# Line 337  initial default for the command---one th Line 338  initial default for the command---one th
338  @code{grep}, so as to search every file in a directory tree.  See also  @code{grep}, so as to search every file in a directory tree.  See also
339  the @code{find-grep-dired} command, in @ref{Dired and Find}.  the @code{find-grep-dired} command, in @ref{Dired and Find}.
340    
341    @node Flymake
342    @section Finding Syntax Errors On The Fly
343    @cindex checking syntax
344    
345      Flymake mode is a minor mode that performs on-the-fly syntax
346    checking for many programming and markup languages, including C, C++,
347    Perl, HTML, and @TeX{}/La@TeX{}.  It is somewhat analogous to Flyspell
348    mode, which performs spell checking for ordinary human languages in a
349    similar fashion (@pxref{Spelling}).  As you edit a file, Flymake mode
350    runs an appropriate syntax checking tool in the background, using a
351    temporary copy of the buffer.  It then parses the error and warning
352    messages, and highlights the erroneous lines in the buffer.  The
353    syntax checking tool used depends on the language; for example, for
354    C/C++ files this is usually the C compiler.  Flymake can also use
355    build tools such as @code{make} for checking complicated projects.
356    
357      To activate Flymake mode, type @kbd{M-x flymake-mode}.  You can move
358    to the errors spotted by Flymake mode with @kbd{M-x
359    flymake-goto-next-error} and @kbd{M-x flymake-goto-prev-error}.  To
360    display any error messages associated with the current line, use
361    @kbd{M-x flymake-display-err-menu-for-current-line}.
362    
363      For more details about using Flymake, see @ref{Top, Flymake,
364    Flymake, flymake, The Flymake Manual}.
365    
366  @node Debuggers  @node Debuggers
367  @section Running Debuggers Under Emacs  @section Running Debuggers Under Emacs
368  @cindex debuggers  @cindex debuggers

Legend:
Removed from v.1.50  
changed lines
  Added in v.1.51

savannah-hackers-public@gnu.org
ViewVC Help
Powered by ViewVC 1.1.26