Re: Bad 'grep' behaviour in -CURRENT, faulty binary detection?

2000-01-04 Thread Ruslan Ermilov
On Fri, Nov 12, 1999 at 20:45:10 -0800, Paul Eggert wrote: Date: Fri, 12 Nov 1999 17:23:21 -0800 From: "David O'Brien" [EMAIL PROTECTED] I assume "--ignore-binary" or "--ignore-binary-files" would be the GNU longopt. Another possibility would be to follow the example of the

Re: Bad 'grep' behaviour in -CURRENT, faulty binary detection?

2000-01-04 Thread Alain Magloire
--n8g4imXOkfNTN/H1 Content-Type: text/plain; charset=us-ascii On Fri, Nov 12, 1999 at 20:45:10 -0800, Paul Eggert wrote: Date: Fri, 12 Nov 1999 17:23:21 -0800 From: "David O'Brien" [EMAIL PROTECTED] I assume "--ignore-binary" or "--ignore-binary-files" would be the

Re: Bad 'grep' behaviour in -CURRENT, faulty binary detection?

2000-01-04 Thread Paul Eggert
Thanks for implementing the result of our earlier discussion. I documented what you wrote, and as a result I have the following suggestions for further improvements: * The assignment to not_text should depend on out_quiet if no --binary-files option is given. * The operands of

Re: Bad 'grep' behaviour in -CURRENT, faulty binary detection?

1999-11-12 Thread David O'Brien
On Fri, Nov 12, 1999 at 12:11:22AM -0800, Paul Eggert wrote: Date: Thu, 11 Nov 1999 23:39:10 -0800 From: "David O'Brien" [EMAIL PROTECTED] Would it be possible to either ignore binary files when "-l" is in affect. OR to add an ignore binary file flag (like FreeBSD has in

Re: Bad 'grep' behaviour in -CURRENT, faulty binary detection?

1999-11-12 Thread David O'Brien
On Thu, Nov 11, 1999 at 09:13:54PM -0500, Alain Magloire wrote: Of course, you can. But I will join my voice to Paul and ask you not to. This behaviour was a long standing request/grip where for example one would do grep pattern * and have the terminal going bananas, if pattern was

Re: Bad 'grep' behaviour in -CURRENT, faulty binary detection?

1999-11-12 Thread Paul Eggert
Date: Fri, 12 Nov 1999 09:08:24 -0800 From: "David O'Brien" [EMAIL PROTECTED] I want a silent ignore of binary files. It'd be reasonable to add an option to do this, after the feature freeze is over and 2.4 comes out. I think it should take an option to not ignore binary files. I

Re: Bad 'grep' behaviour in -CURRENT, faulty binary detection?

1999-11-12 Thread David O'Brien
On Fri, Nov 12, 1999 at 03:39:43PM -0800, Paul Eggert wrote: Date: Fri, 12 Nov 1999 09:08:24 -0800 From: "David O'Brien" [EMAIL PROTECTED] I want a silent ignore of binary files. It'd be reasonable to add an option to do this, after the feature freeze is over and 2.4 comes out.

Re: Bad 'grep' behaviour in -CURRENT, faulty binary detection?

1999-11-12 Thread Alain Magloire
Bonjour M. David O'Brien FreeBSD's previous grep had a "-a" flag to ignore binary files. Thus I'm trying to find a replacement for the old ``grep -al'' usage. In the coming 2.4, if this is such problem for you, there is en environ variable, that will restore the 2.0 behaviour(everything

Re: Bad 'grep' behaviour in -CURRENT, faulty binary detection?

1999-11-12 Thread Alain Magloire
Bonjour M. David O'Brien On Fri, Nov 12, 1999 at 03:39:43PM -0800, Paul Eggert wrote: Date: Fri, 12 Nov 1999 09:08:24 -0800 From: "David O'Brien" [EMAIL PROTECTED] I want a silent ignore of binary files. It'd be reasonable to add an option to do this, after the feature

Re: Bad 'grep' behaviour in -CURRENT, faulty binary detection?

1999-11-12 Thread David O'Brien
On Fri, Nov 12, 1999 at 08:09:24PM -0500, Alain Magloire wrote: Cool! :-) Would you able to reserve the option's letter and GNU-style long name now? I'd like to add this feature to GNU Grep 2.3 in FreeBSD. -a, --text is already taken. I assume "--ignore-binary" or

Bad 'grep' behaviour in -CURRENT, faulty binary detection?

1999-11-11 Thread Thomas Stromberg
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. This only seems to affect -CURRENT because -STABLE runs GNU grep 2.0. (This was committed October 28th).

Re: Bad 'grep' behaviour in -CURRENT, faulty binary detection?

1999-11-11 Thread David O'Brien
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.

Re: Bad 'grep' behaviour in -CURRENT, faulty binary detection?

1999-11-11 Thread Thomas Stromberg
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

Re: Bad 'grep' behaviour in -CURRENT, faulty binary detection?

1999-11-11 Thread Paul Eggert
Date: Thu, 11 Nov 1999 15:29:05 -0500 From: Thomas Stromberg [EMAIL PROTECTED] I just happened to notice this today. For some reason 'grep' seems to think that 'set' output is binary, not text. Most likely this is because the output of your `set' command contains binary data. In

Re: Bad 'grep' behaviour in -CURRENT, faulty binary detection?

1999-11-11 Thread Paul Eggert
Date: Thu, 11 Nov 1999 13:20:32 -0800 From: "David O'Brien" [EMAIL PROTECTED] 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

Re: Bad 'grep' behaviour in -CURRENT, faulty binary detection?

1999-11-11 Thread Dan Nelson
In the last episode (Nov 11), Paul Eggert said: Most likely this is because the output of your `set' command contains binary data. In the past, this has been reported by people whose `set' command would output something like this: IFS=' ^@' where the `^@' in my message denotes a

Re: Bad 'grep' behaviour in -CURRENT, faulty binary detection?

1999-11-11 Thread Alain Magloire
Bonjour M. David O'Brien 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. If I

Re: Bad 'grep' behaviour in -CURRENT, faulty binary detection?

1999-11-11 Thread Alain Magloire
Bonjour M. Peter Jeremy On 1999-Nov-12 13:13:54 +1100, Alain Magloire wrote: (On Solaris, you can read() a directory). On any real Unix you can read() a directory - `everything is a file'. Yes, and real programmers do not eat quiche either. For the Solaris comment, maybe I'm mistaken,