X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.0 required=5.0	tests=AWL,BAYES_00,T_RP_MATCHES_RCVD
X-Spam-Check-By: sourceware.org
From: "Tischler, Ron" <ron DOT tischler AT hp DOT com>
To: "cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Date: Tue, 3 Aug 2010 01:19:25 +0000
Subject: Changed line terminator behavior for grep
Message-ID: <F108D776A6294843B0CEAF4D6364C79A4B500BC66B@GVW1096EXB.americas.hpqcorp.net>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com


It appears that grep's line termination behavior has changed.
Version 2.5.4-2 of grep ends lines with carriage return and linefeed.
Version 2.6.3-1 of grep only puts a linefeed.
I'm curious to know if this is a bug that will be fixed, or if this is the =
desired new behavior.
I'm running  both of them in the same place (a Vista machine).

If that doesn't sound right, here are more details.  I had previously insta=
lled Cygwin 1.6 last year.  Today, I wanted to get something else from Cygw=
in, so that automatically updated things to Cygwin 1.7.5.  Then, test cases=
 that compared output files against previous reference files stopped workin=
g.  The difference was that the old ones had a carriage return and line fee=
d on each line, and the new ones only had a linefeed.  I noticed that this =
only affected tests where the output files were created by grep.  Sure enou=
gh, I went back to Cygwin, and saw that there were two choices for grep (as=
 shown above).  I reinstalled the older version of grep from Cygwin and the=
 tests started working again.  I believe this shows that it is a difference=
 in the behaviors of the two versions of grep, when either one is simply in=
stalled from Cygwin without doing anything tricky.

I don't know if this has been reported before.  I tried to figure out how t=
o search the Cygwin archives, but didn't succeed.=20

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