Date: Thu, 11 Nov 1999 16:37:08 -0800 (PST) From: Paul Eggert <eggert@twinsun.com> To: obrien@freebsd.org Cc: tstromberg@rtci.com, freebsd-current@freebsd.org, bug-gnu-utils@gnu.org Subject: Re: Bad 'grep' behaviour in -CURRENT, faulty binary detection? Message-ID: <199911120037.QAA06642@shade.twinsun.com> In-Reply-To: <19991111132031.A60417@dragon.nuxi.com> (obrien@freebsd.org) References: <382B2711.E13A1CC8@rtci.com> <19991111132031.A60417@dragon.nuxi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Date: Thu, 11 Nov 1999 13:20:32 -0800 From: "David O'Brien" <obrien@freebsd.org> I've got a notion to change this. Please don't change the algorithm to deduce which files are binary. It was the subject of much design discussion in the GNU project, and is fairly consistent across other GNU applications. 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. I find it useful to see the names of all files matching the pattern. This is particularly the case with grep -r. grep -lr should not output a bunch of error messages saying ``Binary file FOO skipped'', as that information is less useful than simply either reporting the file as matching, or not reporting it because it doesn't match. I can't imagine how many people are going to get weird/eronious output from scripts now due to it. The binary file behavior was added to grep in response to many user requests. Users didn't like seeing a lot of binary data sent to their screens. grep's new `-r' option seems to have contributed a lot more requests of this form. 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?199911120037.QAA06642>