[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Emacs-diffs] Changes to emacs/man/building.texi
From: |
Juri Linkov |
Subject: |
[Emacs-diffs] Changes to emacs/man/building.texi |
Date: |
Sun, 14 Aug 2005 04:06:05 -0400 |
Index: emacs/man/building.texi
diff -c emacs/man/building.texi:1.67 emacs/man/building.texi:1.68
*** emacs/man/building.texi:1.67 Wed Aug 10 15:14:29 2005
--- emacs/man/building.texi Sun Aug 14 08:06:03 2005
***************
*** 49,64 ****
@item M-x recompile
Invoke a compiler with the same command as in the last invocation of
@kbd{M-x compile}.
- @item M-x grep
- Run @code{grep} asynchronously under Emacs, with matching lines
- listed in the buffer named @samp{*grep*}.
- @item M-x grep-find
- @itemx M-x find-grep
- Run @code{grep} via @code{find}, with user-specified arguments, and
- collect output in the buffer named @samp{*grep*}.
@item M-x kill-compilation
! @itemx M-x kill-grep
! Kill the running compilation or @code{grep} subprocess.
@end table
@findex compile
--- 49,56 ----
@item M-x recompile
Invoke a compiler with the same command as in the last invocation of
@kbd{M-x compile}.
@item M-x kill-compilation
! Kill the running compilation subprocess.
@end table
@findex compile
***************
*** 324,336 ****
@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
with 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)
--- 316,340 ----
@node Grep Searching
@section Searching with Grep under Emacs
Just as you can run a compiler from Emacs and then visit the lines
with 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.''
! @table @kbd
! @item M-x grep
! Run @code{grep} asynchronously under Emacs, with matching lines
! listed in the buffer named @samp{*grep*}.
! @item M-x grep-find
! @itemx M-x find-grep
! Run @code{grep} via @code{find}, with user-specified arguments, and
! collect output in the buffer named @samp{*grep*}.
! @item M-x kill-grep
! Kill the running @code{grep} subprocess.
! @end table
!
! @findex grep
! To run @code{grep}, 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)