From owner-freebsd-ports@FreeBSD.ORG Sat Aug 16 03:31:41 2003 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9D2B437B404 for ; Sat, 16 Aug 2003 03:31:41 -0700 (PDT) Received: from freebsd2.nitanee.net (statecollegecable-64-178-98-203.ceinetworks.com [64.178.98.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 577D743F3F for ; Sat, 16 Aug 2003 03:31:40 -0700 (PDT) (envelope-from carl@freebsd2.nitanee.net) Received: by freebsd2.nitanee.net (Postfix, from userid 1001) id 565222141; Sat, 16 Aug 2003 06:32:01 -0400 (EDT) Date: Sat, 16 Aug 2003 06:32:01 -0400 From: Carl Cotner To: ports@FreeBSD.org Message-ID: <20030816103201.GA75004@nitanee.net> References: <20030816075253.GA62501@nitanee.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030816075253.GA62501@nitanee.net> User-Agent: Mutt/1.5.4i Subject: Re: port bug: agrep 2.02 on FreeBSD 5.1 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Aug 2003 10:31:41 -0000 Ah, sorry, I figured it out myself! The agrep from the glimpse port works perfectly (and is version 3)! Thanks. - Carl On Sat, Aug 16, 2003 at 03:52:53AM -0400, Carl Cotner wrote: >Hi, > >I have encountered the following bug with agrep 2.04 on FreeBSD 5.1. >The bug does not appear on FreeBSD 4.2. > >I have address files whose format is address - blank line - address - >blank line - etc, like so (Name 1 begins in column 1 in the file): > > Name1 > Address1 > City1, State1 Zip1 > > Name2 > Address2 > City2, State2 Zip2 > > ... > >The following command > > agrep -h -i -t -d '$$' Name address_file > >produces the following output (The first line is missing the first two >characters): > > me1 > Address1 > City1, State1 Zip1 > > Name2 > Address2 > City2, State2 Zip2 > > ... > >As I said, this bug does not appear on FreeBSD 4.2. > >Thanks for all the great work you guys do! >