[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: |
Tue, 09 Aug 2005 17:48:13 -0400 |
Index: emacs/man/building.texi
diff -c emacs/man/building.texi:1.65 emacs/man/building.texi:1.66
*** emacs/man/building.texi:1.65 Thu Jun 23 01:22:28 2005
--- emacs/man/building.texi Tue Aug 9 21:48:12 2005
***************
*** 52,58 ****
Run @code{grep} asynchronously under Emacs, with matching lines
listed in the buffer named @samp{*grep*}.
@item M-x grep-find
! @item 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
--- 52,58 ----
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
***************
*** 325,331 ****
@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.''
--- 325,331 ----
@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.''
- [Emacs-diffs] Changes to emacs/man/building.texi,
Juri Linkov <=