[Emacs-diffs] Changes to emacs/man/building.texi

[Richard M . Stallman]

Index: emacs/man/building.texi
diff -c emacs/man/building.texi:1.48 emacs/man/building.texi:1.49
*** emacs/man/building.texi:1.48        Mon Mar 14 10:00:58 2005
--- emacs/man/building.texi     Mon Mar 21 18:06:58 2005
***************
*** 14,23 ****
  @menu
  * Compilation::         Compiling programs in languages other
                            than Lisp (C, Pascal, etc.).
- * Grep Searching::      Running grep as if it were a compiler.
  * Compilation Mode::    The mode for visiting compiler errors.
  * Compilation Shell::   Customizing your shell properly
                            for use in the compilation buffer.
  * Debuggers::         Running symbolic debuggers for non-Lisp programs.
  * Executing Lisp::      Various modes for editing Lisp programs,
                            with different facilities for running
--- 14,23 ----
  @menu
  * Compilation::         Compiling programs in languages other
                            than Lisp (C, Pascal, etc.).
  * Compilation Mode::    The mode for visiting compiler errors.
  * Compilation Shell::   Customizing your shell properly
                            for use in the compilation buffer.
+ * Grep Searching::      Searching with grep.
  * Debuggers::         Running symbolic debuggers for non-Lisp programs.
  * Executing Lisp::      Various modes for editing Lisp programs,
                            with different facilities for running
***************
*** 147,182 ****
  the form @code{"@address@hidden"}.  These environment
  variable settings override the usual ones.
  
- @node Grep Searching
- @section Searching with Grep under Emacs
- 
- @findex grep
-   Just as you can run a compiler from Emacs and then visit the lines
- where there were compilation errors, you can also run @code{grep} and
- then visit the lines on which matches were found.  This works by
- treating the matches reported by @code{grep} as if they were ``errors.''
- 
-   To do this, type @kbd{M-x grep}, then enter a command line that
- specifies how to run @code{grep}.  Use the same arguments you would give
- @code{grep} when running it normally: a @code{grep}-style regexp
- (usually in single-quotes to quote the shell's special characters)
- followed by file names, which may use wildcards.  The output from
- @code{grep} goes in the @samp{*grep*} buffer.  You can find the
- corresponding lines in the original files using @kbd{C-x `} and
- @key{RET}, as with compilation errors.
- 
-   If you specify a prefix argument for @kbd{M-x grep}, it figures out
- the tag (@pxref{Tags}) around point, and puts that into the default
- @code{grep} command.
- 
- @findex grep-find
- @findex find-grep
-   The command @kbd{M-x grep-find} (also available as @kbd{M-x
- find-grep}) is similar to @kbd{M-x grep}, but it supplies a different
- initial default for the command---one that runs both @code{find} and
- @code{grep}, so as to search every file in a directory tree.  See also
- the @code{find-grep-dired} command, in @ref{Dired and Find}.
- 
  @node Compilation Mode
  @section Compilation Mode
  
--- 147,152 ----
***************
*** 199,204 ****
--- 169,189 ----
  This command is used in the compilation buffer.
  @item Mouse-2
  Visit the locus of the error message that you click on.
+ @item M-n
+ Find and highlight the locus of the next error message, without
+ selecting the source buffer.
+ @item M-p
+ Find and highlight the locus of the previous error message, without
+ selecting the source buffer.
+ @item address@hidden
+ Move point to the next error for a different file than the current
+ one.
+ @item address@hidden
+ Move point to the previous error for a different file than the current
+ one.
+ @item C-c C-f
+ Toggle Next Error Follow minor mode, which makes cursor motion in the
+ compilation buffer produce automatic source display.
  @end table
  
  @kindex C-x `
***************
*** 209,220 ****
  click @kbd{Mouse-2} on the error message; you need not switch to the
  @samp{*compilation*} buffer first.
  
    To parse the compiler error messages sequentially, type @kbd{C-x `}
  (@code{next-error}).  The character following the @kbd{C-x} is the
  backquote or ``grave accent,'' not the single-quote.  This command is
! available in all buffers, not just in @samp{*compilation*}; it displays
! the next error message at the top of one window and source location of
! the error in another window.
  
    The first time @kbd{C-x `} is used after the start of a compilation,
  it moves to the first error's location.  Subsequent uses of @kbd{C-x `}
--- 194,208 ----
  click @kbd{Mouse-2} on the error message; you need not switch to the
  @samp{*compilation*} buffer first.
  
+ @vindex next-error-highlight
    To parse the compiler error messages sequentially, type @kbd{C-x `}
  (@code{next-error}).  The character following the @kbd{C-x} is the
  backquote or ``grave accent,'' not the single-quote.  This command is
! available in all buffers, not just in @samp{*compilation*}; it
! displays the next error message at the top of one window and source
! location of the error in another window.  It also momentarily
! highlights the relevant source line.  You can change the behavior of
! this highlighting with the variable @code{next-error-highlight}.
  
    The first time @kbd{C-x `} is used after the start of a compilation,
  it moves to the first error's location.  Subsequent uses of @kbd{C-x `}
***************
*** 245,254 ****
  that list.  A similar variable @code{grep-regexp-alist} tells Emacs how
  to parse output of a @code{grep} command.
  
    Compilation mode also redefines the keys @key{SPC} and @key{DEL} to
! scroll by screenfuls, and @kbd{M-n} and @kbd{M-p} to move to the next or
! previous error message.  You can also use @address@hidden and @address@hidden 
to
! move up or down to an error message for a different source file.
  
    The features of Compilation mode are also available in a minor mode
  called Compilation Minor mode.  This lets you parse error messages in
--- 233,257 ----
  that list.  A similar variable @code{grep-regexp-alist} tells Emacs how
  to parse output of a @code{grep} command.
  
+ @findex compilation-next-error
+ @findex compilation-previous-error
+ @findex compilation-next-file
+ @findex compilation-previous-file
    Compilation mode also redefines the keys @key{SPC} and @key{DEL} to
! scroll by screenfuls, and @kbd{M-n} (@code{compilation-next-error})
! and @kbd{M-p} (@code{compilation-previous-error}) to move to the next
! or previous error message.  You can also use @address@hidden
! (@code{compilation-next-file} and @address@hidden
! (@code{compilation-previous-file}) to move up or down to an error
! message for a different source file.
! 
! @cindex Next Error Follow mode
! @findex next-error-follow-minor-mode
!   You can type @kbd{C-c C-f} to toggle Next Error Follow mode.  In
! this minor mode, ordinary cursor motion in the compilation buffer
! automatically updates the source buffer.  For instance, moving the
! cursor to the next error message causes the location of that error to
! be displayed immediately.
  
    The features of Compilation mode are also available in a minor mode
  called Compilation Minor mode.  This lets you parse error messages in
***************
*** 298,303 ****
--- 301,342 ----
  wait until the command finishes before you can do anything else in
  Emacs.  @xref{MS-DOS}.
  
+ @node Grep Searching
+ @section Searching with Grep under Emacs
+ 
+ @findex grep
+   Just as you can run a compiler from Emacs and then visit the lines
+ where there were compilation errors, you can also run @code{grep} and
+ then visit the lines on which matches were found.  This works by
+ treating the matches reported by @code{grep} as if they were ``errors.''
+ 
+   To do this, type @kbd{M-x grep}, then enter a command line that
+ specifies how to run @code{grep}.  Use the same arguments you would give
+ @code{grep} when running it normally: a @code{grep}-style regexp
+ (usually in single-quotes to quote the shell's special characters)
+ followed by file names, which may use wildcards.  If you specify a
+ prefix argument for @kbd{M-x grep}, it figures out the tag
+ (@pxref{Tags}) around point, and puts that into the default
+ @code{grep} command.
+ 
+   The output from @code{grep} goes in the @samp{*grep*} buffer.  You
+ can find the corresponding lines in the original files using @kbd{C-x
+ `}, @key{RET}, and so forth, just like compilation errors.
+ 
+   Some grep programs accept a @samp{--color} option to output special
+ markers around matches for the purpose of highlighting.  You can make
+ use of this feature by setting @code{grep-highlight-matches} to t.
+ When displaying a match in the source buffer, the exact match will be
+ highlighted, instead of the entire source line.
+ 
+ @findex grep-find
+ @findex find-grep
+   The command @kbd{M-x grep-find} (also available as @kbd{M-x
+ find-grep}) is similar to @kbd{M-x grep}, but it supplies a different
+ initial default for the command---one that runs both @code{find} and
+ @code{grep}, so as to search every file in a directory tree.  See also
+ the @code{find-grep-dired} command, in @ref{Dired and Find}.
+ 
  @node Debuggers
  @section Running Debuggers Under Emacs
  @cindex debuggers
***************
*** 307,312 ****
--- 346,352 ----
  @cindex SDB
  @cindex XDB
  @cindex Perldb
+ @cindex bashdb
  @cindex JDB
  @cindex PDB
  
***************
*** 366,371 ****
--- 406,415 ----
  requires a valid tags table to work}.  If this happens, generate a valid
  tags table in the working directory and try again.
  
+ @item M-x bashdb @key{RET} @var{file} @key{RET}
+ @findex bashdb
+ Run the bash debugger to debug @var{file}, a shell script.
+ 
  @item M-x perldb @key{RET} @var{file} @key{RET}
  @findex perldb
  Run the Perl interpreter in debug mode to debug @var{file}, a Perl program.
***************
*** 1046,1051 ****
--- 1090,1099 ----
  echo area.  It is available in all major modes, not just Emacs-Lisp
  mode.  It does not treat @code{defvar} specially.
  
+   When the result of an evaluation is an integer, you can type
+ @kbd{C-x C-e} a second time to display the value of the integer result
+ in additional formats (octal, hexadecimal, and character).
+ 
    If @kbd{C-M-x}, @kbd{C-x C-e}, or @kbd{M-:} is given a numeric
  argument, it inserts the value into the current buffer at point, rather
  than displaying it in the echo area.  The argument's value does not