David O'Brien wrote:
>
> 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.
>
I think it's good as a default, nothing annoys me more then "grep -R
function *" in a source directory and hitting all the binaries and
getting my screen splattered with high ascii. I just wish it's binary
detection was a wee bit more accurate..
I don't see what's wrong with "grep -l", it does exactly what I expected
it to do. It's just expected to tell you that a file matched, not
anything more (anything more could cause grave problems with scripts,
including some I've written)..
[root@karma] /tmp> grep -l expat *
expat
expat-0.7.6.tar.gz
wv
(or maybe I'm just not understanding the issue).
--
======================================================================
thomas r. stromberg smtp:[EMAIL PROTECTED]
assistant is manager / systems guru http://thomas.stromberg.org
research triangle commerce, inc. finger:[EMAIL PROTECTED]
'om mani pedme hung' pots://1.919.380.9771:3210
================================================================[eof]=
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
