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:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=OebF8Q61PlH53DI9
	qz73/sDcaiLiRlbl8YIiY3JVEd68yw2YG3iNKda8/L2LzcAS4YCfWQ3b5xWC7/mL
	c+Zq1x0HmP2a7kp5RcQxukACzqf81veJdR84f4jrUHrnjcpOnJn+YfZgTFcmMNBo
	uVHbCSi26noqPk0Q09tRaycoUYM=
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: 2.10.0: Cygwin now can not work well with a file in dos format.
To: cygwin AT cygwin DOT com
References: <2bfeabde DOT 39a8 DOT 16403e31153 DOT Coremail DOT tuyanyi AT 163 DOT com> <0F7D3B1B3C4B894D824F5B822E3E5A177880092C AT IRSMSX102 DOT ger DOT corp DOT intel DOT com> <003101d40572$dcd479f0$967d6dd0$@rogers.com>
From: Marco Atzeri <marco DOT atzeri AT gmail DOT com>
Message-ID: <9e083c12-dc2d-dc92-1553-aabb5dea4390@gmail.com>
Date: Sat, 16 Jun 2018 15:32:46 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <003101d40572$dcd479f0$967d6dd0$@rogers.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

On 6/16/2018 3:06 PM, Michel LaBarre wrote:
> 

> 
> [Michel LaBrre:]
> I also find the decision unfortunate as I am one of the many riff-raff who use Cygwin to supplement windows
> and have no need for strict POSIX compliance but then I get what I pay for :-)  In any event I have a few
> questions:
> 
>    1. Where in the release notes is this mentioned so that I can try to ensure that I find out about future changes?
>         Searching for Cygwin release notes gets me to https://cygwin.com/cygwin-ug-net/ov-new.html
>         In which I have found no (or could not recognise) mention of no longer stripping CR.
>         Are there more detailed release notes somewhere else?

https://sourceware.org/ml/cygwin-announce/2017-02/msg00020.html for sed

> 
>    2. Various "solutions" have been noted for gawk in related emails - all require minor but pervasive code changes.
>        Are there any similar solutions for the other tools besides scattering "tr" all over the place?
>        Is everything affected from sort to grep to join?  This could impact the use of such tools with multiple files
>        some of which come from Win32 tools and others from Cygwin tools.  I may be wrong about the
>        pervasiveness of the impact since, as I said, nothing was apparent in the release notes that I found.
> 
>        Also, I don't recall seeing related discussions in this mail-list.  Would these have taken place in
>        another Cygwin-developer-focused mail-list?

no. here

my solution is to use d2u and u2d of dos2unix package
for moving files between the two formats.


>    3. Is there any chance of Cygwin providing a pervasive file behaviour control switch for all the affected tools
>       that have been used generally for text rather than binary data handling?

LF and CRLF format files are both text but in different environments

> 
>    4. Would MSYS be better for those of us who are trying to supplement Windows rather than running Linux
>         on Windows?

it depends on your preference.

> 
> Thanks,
> /Michel
>        

--
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