This is the mail archive of the
mailing list for the Cygwin project.
Re: Change in command line behavior between cygwin 1.3.18-1 and 1.3.19-1
- From: Paul Coltrin <pablo at projtech dot com>
- To: cygwin at cygwin dot com
- Date: Mon, 24 Feb 2003 15:59:22
- Subject: Re: Change in command line behavior between cygwin 1.3.18-1 and 1.3.19-1
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 -
(These are both conditions I would like to preserve in order to minimize
porting and maitainability issues.)
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
>> On Cygwin we have been using the pdksh (
>> http://www.cs.mun.ca/~michael/pdksh/ ).
>> Here is a sample script:
>> 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?
>elfyn at exposure dot org dot uk
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html