Date: Thu, 11 Nov 1999 13:20:32 -0800 From: "David O'Brien" <obrien@freebsd.org> To: Thomas Stromberg <tstromberg@rtci.com> Cc: freebsd-current@freebsd.org, bug-gnu-utils@gnu.org Subject: Re: Bad 'grep' behaviour in -CURRENT, faulty binary detection? Message-ID: <19991111132031.A60417@dragon.nuxi.com> In-Reply-To: <382B2711.E13A1CC8@rtci.com>; from tstromberg@rtci.com on Thu, Nov 11, 1999 at 03:29:05PM -0500 References: <382B2711.E13A1CC8@rtci.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Nov 11, 1999 at 03:29:05PM -0500, Thomas Stromberg wrote: > I just happened to notice this today. For some reason 'grep' seems to > think that 'set' output is binary, not text. Seems that GNU grep 2.3 is > a little too sensitive to text/binary detection. I've got a notion to change this. The -CURRENT grep is also very misleading w/ ``grep -l'' in that you will get "hits" on binary files because you can't see that "is a binary file" message to know better. The output of that message should be asked for with an option, not the default. I can't imagine how many people are going to get weird/eronious output from scripts now due to it. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19991111132031.A60417>