X-Spam-Check-By: sourceware.org Subject: RE: Problem with Text mounts after updating using setup.exe MIME-Version: 1.0 Date: Mon, 20 Aug 2007 10:40:34 +0200 Message-ID: <30593C81E890114EAC2DCAE5AC7E5C9901877923@GDEXCH6.ortec.intranet> In-Reply-To: <30593C81E890114EAC2DCAE5AC7E5C990183B941@GDEXCH6.ortec.intranet> From: "Bart van der Werf" To: Content-Type: text/plain; charset="us-ascii" X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id l7K8biRW023984 Could someone confirm this is introduced in grep-2.5.1a-4, grep-2.5.1a-2 seems to be good? Greets, Bart > -----Original Message----- > From: Bart van der Werf > Sent: Wednesday, August 15, 2007 10:44 AM > To: cygwin AT cygwin DOT com > Subject: Problem with Text mounts after updating using setup.exe > > After upgrading cygwin some of my textmode mount files > started to have additional 0x0d characters. > > Example of problem. > > With a file test.txt > > $ od -t x1 test.txt > 0000000 61 0d 0a 62 0d 0a 63 0d 0a > 0000011 > > with dos style newlines. > > $ grep a test.txt > test2.txt > > If i invoke grep on this file, i get the problem that it > duplicates the 0x0d > > $ od -t x1 test2.txt > 0000000 61 0d 0d 0a > 0000004 > > I started getting this problem after running setup.exe this week. > > The version of cygwin before the upgrade was atleast a year old. > > What should i do ? > Do i need to provide additional information ? > > I wouldn't expect an additional 0x0d even if the mount was in binmode. > > greeting Bart van der Werf > -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/