Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: <016b01c2daa0$17ddf580$666d86d9@webdev> From: "Elfyn McBratney" To: "cygwin" , "Paul Coltrin" References: <3.0.6.32.20030221130139.00a80550@phoenix.projtech.com> Subject: Re: Change in command line behavior between cygwin 1.3.18-1 and 1.3.19-1 Date: Sat, 22 Feb 2003 18:27:43 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 > I am hoping that someone can explain this change of behavior I have > noticed that occurred between Cygwin version 1.3.18-1 and 1.3.19-1. > > In order to remain compatible with MKS, and also to keep version control > as simple as possible we need to continue using ksh to execute our scripts. > On Cygwin we have been using the pdksh ( > http://www.cs.mun.ca/~michael/pdksh/ ). > > Here is a sample script: > --- > #!/bin/ksh > set +u > --- Hello, I just tried your testscript and it works under 1.3.20 . Perhaps upgrading to the latest version of the cygwin1.dll would fix your problem? Regards, Elfyn McBratney elfyn@exposure.org.uk www.exposure.org.uk -- 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/