Message-Id:	<m0xQWdm-000S2YC@inti.gov.ar>
Comments:	Authenticated sender is <salvador AT natacha DOT inti DOT gov DOT ar>
From:	"Salvador Eduardo Tropea (SET)" <salvador AT inti DOT edu DOT ar>
Organization:	INTI
To:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>, djgpp AT delorie DOT com
Date:	Wed, 29 Oct 1997 14:56:27 +0000
MIME-Version:	1.0
Subject:	Re: subdirectories (was: ANNOUNCE: Grep 2.1 uploaded)

Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> wrote:
> 
> On Tue, 28 Oct 1997, Salvador Eduardo Tropea (SET) wrote:
> 
> > 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!
> 
> Sorry, I don't understand this.  What huge difference are you talking
> about here?
> 
Easy to use, easy to learn, execellent results, etc.

> > 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?
> 
> Mostly, yes, but not always.  For example, I almost always use `fgrep'
> instead of `grep', because it is faster if you look for fixed
> strings.  Sometimes I need to find only hits that are words (not
> substrings), so I use the -w switch.  And there are other examples.
-w and the switch for fgrep are supported in my shell, you just select the 
options.
Additionally the list of strings for fgrep can be taked from the clipboard of 
the editor or from a file making it more flexible (you select part of a list, 
make Paste and you have a subset to use in the search).

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 -