procyberian/emacs
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Minor copyedits in efaq-w32

Browse source 
* doc/misc/efaq-w32.texi (Grep, Recursive grep): More accurate
description of using 'findstr' as a poor-man's replacement for
'grep'.  Reported by 范凯 <m_pupil@163.com>
This commit is contained in:
Eli Zaretskii 2019-06-08 18:48:33 +03:00
parent 48422af0f3
commit b58ecafcdc
1 changed files with 4 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

6
doc/misc/efaq-w32.texi
View file

@ -1820,7 +1820,8 @@ If you want a quick solution without installing extra tools, a poor
substitute that works for simple text searches is to specify the built substitute that works for simple text searches is to specify the built
in Windows command @command{findstr} as the command to run at the in Windows command @command{findstr} as the command to run at the
@kbd{M-x grep} prompt. Normally you will want to use the @option{/n} @kbd{M-x grep} prompt. Normally you will want to use the @option{/n}
argument to @command{findstr}. argument to @command{findstr}, to have it print the line numbers for
each hit.
@menu @menu
* Recursive grep:: * Recursive grep::
@ -1860,7 +1861,8 @@ path to the findutils @command{find} command.
An alternative if you have a recent version of grep is to customize An alternative if you have a recent version of grep is to customize
@code{grep-find-command} to use @samp{grep -r} instead of both find @code{grep-find-command} to use @samp{grep -r} instead of both find
and grep. Another alternative if you don't need the full capabilities and grep. Another alternative if you don't need the full capabilities
of grep is to use @samp{findstr /n /r}. of grep is to use @samp{findstr /n /r}; add the @samp{/s} option if
you want a recursive search.
@c ------------------------------------------------------------ @c ------------------------------------------------------------
@node Developing with Emacs @node Developing with Emacs