Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site ttrdc.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxn!ihnp4!ltuxa!ttrdc!levy
From: levy@ttrdc.UUCP (Daniel R. Levy)
Newsgroups: net.unix
Subject: Re: Need unix command file HELP!
Message-ID: <724@ttrdc.UUCP>
Date: Sun, 9-Feb-86 00:19:13 EST
Article-I.D.: ttrdc.724
Posted: Sun Feb  9 00:19:13 1986
Date-Received: Tue, 11-Feb-86 06:10:01 EST
References: <245@aero.ARPA> <2981@umcp-cs.UUCP>
Organization: AT&T, Computer Systems Division, Skokie, IL
Lines: 28
Keywords: Unix, string search, Sake o nomimasu ka?

<Oh oh here it comes.  Watch out boy, it'll chew you up! \
Oh oh here it comes.  The LINE EATER!  [Line eater]>

In article <2981@umcp-cs.UUCP>, chris@umcp-cs.UUCP (Chris Torek) writes:
>In article <245@aero.ARPA> sutton@aero.UUCP (Stew Sutton) writes:
>Also easy: just discard error messages from grep.

Not just that; you ALSO want to discard the crap that grep will spit at the
tty if the string wanted is found in a BINARY FILE!  (Some terminals get
VERY UPSET at random binary sequences.)  Better yet, use the '-l' option:

	$ find / -exec {e,f,""}grep -l "pattern" {} \;

(fgrep is best for FIXED patterns that contain characters which egrep and
grep would treat as wild cards.)

>--
>In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 1415)
>UUCP:	seismo!umcp-cs!chris
>CSNet:	chris@umcp-cs		ARPA:	chris@mimsy.umd.edu
-- 
 -------------------------------    Disclaimer:  The views contained herein are
|       dan levy | yvel nad      |  my own and are not at all those of my em-
|         an engihacker @        |  ployer or the administrator of any computer
| at&t computer systems division |  upon which I may hack.
|        skokie, illinois        |
 --------------------------------   Path: ..!{akgua,homxb,ihnp4,ltuxa,mvuxa,
						vax135}!ttrdc!levy