X-Spam-Check-By: sourceware.org Date: Fri, 12 Jan 2007 16:52:56 +1100 (EST) From: Luke Kendall Subject: Re: CR/LF problems after upgrade To: cygwin AT cygwin DOT com In-Reply-To: <8183547.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Message-Id: <20070112055257.55D3083C6F@pessard.research.canon.com.au> 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 On 5 Jan, fschmidt wrote: > > 3. Cygwin text mounts automatically work with either line ending style, > > because the \r is stripped before bash reads the file. If you absolutely > > must use files with \r\n line endings, consider mounting the directory > > where those files live as a text mount. However, text mounts are not as > > well tested or supported on the cygwin mailing list, so you may encounter > > other problems with other cygwin tools in those directories. > > > > I don't know what mounts are, or how to use them. With a freshly-installed Cygwin from a mirror that's a few days old, and with c:\cygwin\bin mounted textmode and a network share directory of bash scripts also mounted in textmode, using scripts that had CR/LF endings, each blank line in the script caused an error, and there were other errors too. In short, I don't think the text mounts are doing their magic correctly at the moment. (The scripts mentioned above did work correctly in much older Cygwins using text mounts.) I wonder how many centuries of human endeavour has been absorbed because of the decision to use CR+LF as line endings in DOS? luke -- 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/