DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; q=dns; s=default; b=oFMiIiXt6rNjOyy0
	I+fWPxy0KJg0tPLgVctP+IiPk7MbdnSeTn4JU1kQ/Ni2odRIED/1MPrjpwLRV0VZ
	PPHH6g4mRHOjuhtwWHw8n7RR9NQdr08Ozx05FgccSAhe+6T7AQgG/4o1RG+Q1RUV
	TYUv5TtJ6ITz5J8pc93Ljh2BH9E=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Fri, 17 Jul 2015 05:30:47 +0300
From: Andrey Repin <anrdaemon@yandex.ru>
Reply-To: cygwin@cygwin.com
Message-ID: <1654709150.20150717053047@yandex.ru>
To: "John Hein" <3fbmqnhaz4@snkmail.com>, cygwin@cygwin.com
Subject: Re: --line-regexp option with null data
In-Reply-To: <6138-1437098652-808922@sneakemail.com>
References: <CAAXzdLWo4nvaJBMOBYsOYeCdrgw_O=8CM_H_kwfxnU=AqnuOjA@mail.gmail.com>   <6138-1437098652-808922@sneakemail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=Windows-1251
Content-Transfer-Encoding: 8bit

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 byte = not a text.
Wrong encoding, not matching locale = not a text.

This is an upstream decision. It is arguable consistent… on Linux.
On Windows, of course, this is not the case.

> As a workaround for this simple example, you can add -a (aka --text)
> to force it to treat the input as text.


-- 
With best regards,
Andrey Repin
Friday, July 17, 2015 05:29:11

Sorry for my terrible english...