Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-Id: <3.0.6.32.20030224155922.00b16870@phoenix.projtech.com>
X-Sender: pablo AT phoenix DOT projtech DOT com
Date: Mon, 24 Feb 2003 15:59:22
To: cygwin AT cygwin DOT com
From: Paul Coltrin <pablo AT projtech DOT com>
Subject: Re: Change in command line behavior between cygwin 1.3.18-1
  and  1.3.19-1
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-MailScanner: not scanned: please contact your email provider for details
X-MailScanner-SpamCheck: 

Elfyn,

Thanks for the reply.

Unfortunately, the behavior also exists in 1.3.20.  I first found it there
and then worked back to narrow down in which version it appeared.

In order to see the problem, the script needs to have DOS-style
line endings, and also it must invoked with an MKS-style path,
ie with a Windows style drive letter but with unix forward slashes -
 C:/cygtest/testscript .

(These are both conditions I would like to preserve in order to minimize
porting and maitainability issues.)

Paul Coltrin
pablo AT projtech DOT com

At 06:27 PM 2/22/03 -0000, you wrote:
>> 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 AT exposure DOT org DOT 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/