Xref: utzoo comp.unix.wizards:8902 comp.unix.questions:7297
Path: utzoo!attcan!uunet!lll-winken!lll-lcc!ames!amdahl!rtech!rain!jas
From: jas@rain.rtech.UUCP (Jim Shankland)
Newsgroups: comp.unix.wizards,comp.unix.questions
Subject: Re: grep replacement
Message-ID: <2123@rtech.UUCP>
Date: 27 May 88 16:07:16 GMT
References: <7882@alice.UUCP> <5630@umn-cs.cs.umn.edu> <6866@elroy.Jpl.Nasa.Gov> <2978@ihlpe.ATT.COM>
Sender: news@rtech.UUCP
Reply-To: jas@rtech.UUCP (Jim Shankland)
Organization: Eddie Enterprises
Lines: 17

In article <2978@ihlpe.ATT.COM> dcon@ihlpe.UUCP (David Connet) writes:
>In article <6866@elroy.Jpl.Nasa.Gov> alan@cogswell.Jpl.Nasa.Gov (Alan S. Mazer) writes:
>>One thing I would _love_ is to be able to find the context of what I've
>>found, for example, to find the two (n?) surrounding lines....
>
>Also, what line number it was found on.

You've already got the line number with the "-n" option.  Note that that makes
it easy to write a little wrapper script that gives you context grep.
Whether that's preferable to adding the context option to grep is, I suppose,
debatable; but I can already see the USENIX paper:

	"newgrep -[whatever] Considered Harmful"

Jim Shankland
  ..!ihnp4!cpsc6a!\
               sun!rtech!jas
 ..!ucbvax!mtxinu!/