X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Steven Brown Subject: Re: Fixing the state of C++ in Cygwin Date: Sun, 16 Apr 2006 20:21:38 -0700 Lines: 15 Message-ID: References: <20060412045300 DOT GB7046 AT trixie DOT casa DOT cgf DOT cx> <443C91B0 DOT 1020806 AT ucsd DOT edu> <20060412103121 DOT GA12493 AT calimero DOT vinschen DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit User-Agent: Thunderbird 1.5 (Windows/20051201) In-Reply-To: X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk 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 Steven Brown wrote: > Steven Brown AT FICTITION ~/src > $ cat << EOF | file - > > foo > > EOF > /dev/stdin: ASCII text, with CRLF line terminators [...] > Is this by design or a bug? It seems like the wrong thing for it to be > doing. The cause of this is apparently /tmp being a textmode mount. If switched to binary, cat << EOF works as expected. Is that really what's supposed to happen? It doesn't seem right that a system configured to act binmode is going textmode just due to using '<< EOF' syntax. -- 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/