On 07/16/2015 08:04 PM, John Hein wrote:
> > printf 'alpha\0bravo\0charlie\0' | grep --line-regexp --quiet bravo
> >
> > My thinking tells me that because I have not used `--null-data`, grep
> should see
> > 1 or even 0 lines separated by newline, and fail to match a `bravo`
> followed b
On Thu, Jul 16, 2015 at 9:04 PM, John Hein wrote:
> cygwin grep is detecting the input as binary which seems to be
> overriding the 'match the whole line' behavior of --line-regexp. Get
> rid of --quiet to see that.
It appears to be intended behavior starting with version 2.21:
> If a file conta
> On Jul 16, 2015, at 10:04 PM, Steven Penny wrote:
>
> On Thu, Jul 16, 2015 at 9:30 PM, Andrey Repin wrote:
>> Linux grep will do the same.
>> null byte = not a text.
>> Wrong encoding, not matching locale = not a text.
>
> I have repeatedly asked you to stay out of my threads. My experience is
On Thu, Jul 16, 2015 at 9:30 PM, Andrey Repin wrote:
> Linux grep will do the same.
> null byte = not a text.
> Wrong encoding, not matching locale = not a text.
I have repeatedly asked you to stay out of my threads. My experience is you
typically misread, misunderstand or misrepresent most or all
Greetings, John Hein!
> cygwin grep is detecting the input as binary which seems to be
> overriding the 'match the whole line' behavior of --line-regexp. Get
> rid of --quiet to see that.
> That does seem like a bug in the cygwin implementation of grep to me.
Linux grep will do the same.
null b
Steven Penny svnpenn-at-gmail.com |cygwin_ml_nodigest| wrote at 20:29 -0500 on
Jul 16, 2015:
> Consider this command:
>
> printf 'alpha\nbravo\ncharlie\n' | grep --line-regexp --quiet bravo
>
> grep sees 3 lines separated by newline, and matches the bravo line. Now
> consider
> this co
6 matches
Mail list logo
