From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: 2.10.0: Cygwin now can not work well with a file in dos format.
Date: Sat, 16 Jun 2018 15:21:00 -0000 [thread overview]
Message-ID: <9e083c12-dc2d-dc92-1553-aabb5dea4390@gmail.com> (raw)
In-Reply-To: <003101d40572$dcd479f0$967d6dd0$@rogers.com>
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
next prev parent reply other threads:[~2018-06-16 13:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-15 16:19 tuyanyi
2018-06-15 19:46 ` Soegtrop, Michael
2018-06-15 23:50 ` cyg Simple
2018-06-16 0:49 ` Brian Inglis
2018-06-16 14:10 ` Michel LaBarre
2018-06-16 15:21 ` Marco Atzeri [this message]
2018-06-16 20:25 ` Soegtrop, Michael
2018-06-16 20:34 ` Michel LaBarre
2018-06-17 1:13 ` cyg Simple
2018-06-15 22:50 ` cyg Simple
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9e083c12-dc2d-dc92-1553-aabb5dea4390@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).