Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Date: Wed, 5 Jun 2002 17:10:24 +0200 From: Pavel Tsekov Reply-To: Pavel Tsekov Organization: Syntrex, Inc. X-Priority: 3 (Normal) Message-ID: <12825541747.20020605171024@syntrex.com> To: Christopher Faylor CC: cygwin AT cygwin DOT com Subject: Re: More 1.3.11 road show In-Reply-To: <20020605034752.GA32174@redhat.com> References: <20020605034752 DOT GA32174 AT redhat DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit [snip] CF> What this means is that if you do something like this: c:\>>pwd > d:\tmp\foo CF> and you've previously done a CF> mount -b d:\tmp /dtmp CF> then the line endings in d:\tmp\foo will be \n rather than \r\n. I've done some simple tests and it works for me. One question though: Consider this situation - I have drive C mounted on /cygdrive/c/ as binary and I have C:\Temp mounted on /ctmp as text. Now redirecting the output of 'pwd' to a file in /cygdrive/c/Temp/ gives me UNIX line endings, while redirecting it to /ctmp gives me DOS line endings. Is this intended ? Shouldn't the /ctmp mount override the settings for /cygdrive/c/Temp ? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/