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, 2 Jul 2003 17:27:38 +0100 From: Elfyn McBratney X-X-Sender: elfyn AT ellixia Reply-To: cygwin AT cygwin DOT com To: Carl Lindgren cc: cygwin AT cygwin DOT com Subject: Re: Question on postinstall In-Reply-To: <00a401c340b5$7ddb05f0$0325a8c0@crlc.net> Message-ID: References: <00a401c340b5$7ddb05f0$0325a8c0 AT crlc DOT net> Mail-Followup-To: cygwin AT cygwin DOT com MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Wed, 2 Jul 2003, Carl Lindgren wrote: > Opps! >>> I did mean EOL and not EOF, sorry for the confusion... > > Like I said in my last post... I don't have a problem with bash or zsh only > with ksh that I compiled on Cygwin. Not a major problem for me but I would > like to know how to correct it. It seems to me, from what I can remember, > that the ksh port from the Microsoft NT 4.0 Resource Kit didn't have this > problem. That's most likely because the Windows NT version used pure "textmode" (CR/LF) when dealing with input and output. > But when I compiled the *nx pdksh on Cygwin that is when I started > to see this problem with ksh. I have "ported" pdksh to Cygwin. Is there any reason why you can't use the version distributed in the net release? Do you have the same problems with the net release version (5.2.14-2)? The distributed version (5.2.14 derived) uses automode for input and output. IIRC, that means reads in textmode/binmode and written in binmode. > Again my mistake on the EOL and EOF thing... Elfyn -- -- 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/