Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sourceware.cygnus.com Delivered-To: mailing list cygwin@sourceware.cygnus.com From: Chris Faylor Date: Sat, 20 May 2000 23:20:35 -0400 To: cygwin@sourceware.cygnus.com Subject: Re: bash sourcing Message-ID: <20000520232035.B6606@cygnus.com> Reply-To: cygwin@sourceware.cygnus.com Mail-Followup-To: cygwin@sourceware.cygnus.com References: <20000521031506.92398.qmail@hotmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000521031506.92398.qmail@hotmail.com>; from tjhorton@hotmail.com on Sat, May 20, 2000 at 10:15:06PM -0500 On Sat, May 20, 2000 at 10:15:06PM -0500, Tim Horton wrote: >Anyone notice that bash in the new cygwin 1.1.1 cannot >source a bash script? My .bashrc files are processed, >though with lots of errors and the outcome is garbled. >All my aliases have quotes in strange places, and it >tries to process comments. We've noted that cygwin 1.1.1 has problems with files that have \r\n line endings. That's why bash has problems. This will be fixed in 1.1.3, which I hope to make available in a couple of days. If you want to test a snapshot to see if it solves your problem go to: http://sourceware.cygnus.com/cygwin/snapshots/ . cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com