DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:reply-to:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=EaAU5Cjdrznv+dQ7
	/CUSGurWATpKmntc0xCvR1I0yI/Zpf4sLWeTbKW9+pBRJUEaKAzjxUB5CWIG2IQE
	BQc4xoasEv/rRTMdNxF8SjlP36AglZlPwHNLjUIAZ7qWiyYu1UI9wjNbox9GVLTW
	IA/CxXzXekmkYb92C/mgSYleqWs=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Subject: Re: Grep can't match characters before EOL marker without ^M
To: cygwin AT cygwin DOT com
References: <CAA5t8Vrr_GcYqaLq-1noAj7mxQ7KsMnd43k10-ef1anuCr60Tg AT mail DOT gmail DOT com> <00e694f3-1e50-24be-95dd-8b6bf2bb1323 AT aol DOT com>
Reply-To: cygwin AT cygwin DOT com
From: cyg Simple <cygsimple AT gmail DOT com>
Message-ID: <d35c9962-66e6-e6ce-12a1-646281f537bf@gmail.com>
Date: Thu, 4 Jan 2018 14:51:19 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2
MIME-Version: 1.0
In-Reply-To: <00e694f3-1e50-24be-95dd-8b6bf2bb1323@aol.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit

On 1/3/2018 1:39 PM, arrl via cygwin wrote:
> On 1/3/2018 12:31 PM, David Karr wrote:
>> My cygwin version appears to be "2.9.0(0.318/5/3)".
>>
>> If I have a text file that has a line that ends with "abc", and I try
>> to grep for "abc$", it doesn't match.  I find that it does match "$"
>> and "abc^M$".
>>
>> I've read some of the documentation about line endings in Cygwin.
>>
>> I need to write some scripting that works on both Cygwin and Linux.
>> What do I need to do here?
>>
> 
> Consider running dos2unix on files containing ^M at line ends.
> 

You might wish to test for a binary file before running dos2unix on it
though or even using sed to substitute ^M$ to remove them.  Binary data
could contain a CRLF that would destroy the binary file if CR is removed.

Also consider doing the same instruction regardless of the OS because
you never know when your script meets a file from a different OS. In the
business world many people send files from Windows to *NIX and vice
versa.  If a text file from *NIX is sent to a user of Windows be sure
that the file contains the appropriate CRLF or the user will just see
garbage unless they are a DevOPS person who knows how to deal with the
file.  I can't count the number of times I've had to resend a file or
help someone adjust one just because the Windows default for .txt files
is Notepad which uses the CR to advance to the next line of the GUI.

-- 
cyg Simple

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple