From owner-freebsd-hackers Wed Jul 7 11:21:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 8910214D7D for ; Wed, 7 Jul 1999 11:21:12 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.1) id UAA89618; Wed, 7 Jul 1999 20:20:53 +0200 (CEST) (envelope-from des) To: Jamie Howard Cc: freebsd-hackers@FreeBSD.ORG, tech-userlevel@netbsd.org, tech@openbsd.org Subject: Re: Replacement for grep(1) (part 2) References: From: Dag-Erling Smorgrav Date: 07 Jul 1999 20:20:53 +0200 In-Reply-To: Jamie Howard's message of "Mon, 5 Jul 1999 21:14:36 -0400 (EDT)" Message-ID: Lines: 33 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jamie Howard writes: > Due to the number of fixes I have received over the past few days, I > decided to put together a new release of grep. It was either this or > watch _Titanic_ on Cinemax. A clear-cut choice. > I changed it so that even when called as grep or with -G, it treats the > pattern as an extended regular expression. GNU grep behaves the same way. Hmm, well, never mind standards I guess. > Archie Cobbs dropped the hint needed to solve the problems with -x. Right > now, I wrap the pattern with "^(" and ")$". I know GNU grep does this, > but is this correct? Yes. You can solve -w in a similar manner by using \< and \>. > Now, as it stands, I beleive this implementation is identical to GNU grep, *functionally* identical. > Due to problems with the previous download site (it is down as I type > this), I will place this file in two locations: > > ftp://dragon.ham.muohio.edu/pub/howardjp/grep-0.3.tar.gz > ftp://ftp.wam.umd.edu/pub/howardjp/grep-0.3.tar.gz Mirror site: ftp://ftp.ofug.org/pub/grep/ DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message