Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Thu, 16 Nov 2000 12:49:06 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: sed and find Message-ID: <20001116124906.A20240@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <200011161653 DOT QAA25955 AT ireserver DOT Ireland DOT Sun DOT COM> <4 DOT 3 DOT 1 DOT 2 DOT 20001116123514 DOT 00b900f8 AT pop DOT ma DOT ultranet DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <4.3.1.2.20001116123514.00b900f8@pop.ma.ultranet.com>; from lhall@rfk.com on Thu, Nov 16, 2000 at 12:39:58PM -0500 On Thu, Nov 16, 2000 at 12:39:58PM -0500, Larry Hall (RFK Partners, Inc) wrote: >At 11:53 AM 11/16/2000, Armin Theissen wrote: >Generally these kinds of problems are due to carriage returns in files, >although the bash and ash versions that come with 1.1.4 should be much better >at making this issue transparent. Ditto, 'sed', actually. This error report sounds like something from cygwin 1.1.1 days. sed, bash, and ash, shouldn't be giving this type of error. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com