Mail Archives: djgpp/1997/10/28/12:45:40
Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> wrote:
> On Mon, 27 Oct 1997, Salvador Eduardo Tropea (SET) wrote:
>
> > I agree with you, for that reason I did a "grep shell", that's a friendly
> > interface to call grep. Additionally it adds the recursion.
>
> No matter how smart and friendly this interface will be, it won't
> support every possible way of using `grep'.
I agree on that but comparing the use of grep alone and grep inside of the
editor makes grep so see like a monster. The shell is to cover the 95% of the
grep use: Search in your files. And here the difference is huge!
> That's why sometimes you
> will need to use `grep' in conjunction with `find'. Using `find' for
> recursively searching subdirectories is of course redundant in DJGPP,
> since we have the "..." wildcard, courtesy of DJ. But `find' can
> choose files it passes to `grep' using much more powerful and
> elaborate tests than you can ever do with `grep' alone. For example,
> you can limit the recursion to a certain depth of subdirectories,
> search only files created within last 2 days, or which are newer than
> a certain file, or larger than N bytes, etc.
And all with cryptic options, I know how to use find since 4 years, but I NEVER
use it because I use other tools that covers the 95-99% of the find use and are
much more easy to use.
Don't you use EMACs when searching in a set of files to jump directly to the
line? Don't you think that this is the most important part?
SET
------------------------------------ 0 --------------------------------
Visit my home page: http://www.geocities.com/SiliconValley/Vista/6552/
Salvador Eduardo Tropea (SET). (Electronics Engineer)
Alternative e-mail: set-sot AT usa DOT net - ICQ: 2951574
Address: Curapaligue 2124, Caseros, 3 de Febrero
Buenos Aires, (1678), ARGENTINA
TE: +(541) 759 0013
- Raw text -