Path: utzoo!utgpu!watserv1!watmath!att!tut.cis.ohio-state.edu!ucbvax!ucsd!sdd.hp.com!samsung!uunet!crdgw1!antarctica!davidsen
From: davidsen@antarctica.crd.GE.COM (william E Davidsen)
Newsgroups: comp.unix.questions
Subject: Re: Unnecessarily long pipelines (was Re: How do you handle while(1) fork(); ?)
Message-ID: <10177@crdgw1.crd.ge.com>
Date: 23 Jul 90 13:48:29 GMT
References: <price.648165820@chakra> <2358@root44.co.uk>
Sender: news@crdgw1.crd.ge.com
Reply-To: davidsen@crdos1.crd.ge.com (bill davidsen)
Organization: GE Corporate R&D Center, Schenectady NY
Lines: 9


In article <2358@root44.co.uk>, gwc@root.co.uk (Geoff Clare) writes:

|> Why is it that people string together lots of "grep" commands in a
|> pipeline, when they could do the same job with a single "sed" or "awk"
|> command?  In this case it's even worse, because "awk" is already in
|> there as well!

  Or egrep, or whatever. Maybe becauses it's easier to type?