Igor,
Yes, I am using textmode mounts:
---
C:\cygwin\bin on /usr/bin type system (textmode)
C:\cygwin\lib on /usr/lib type system (textmode)
C:\cygwin on / type system (textmode)
c: on /cygdrive/c type user (textmode,noumount)
d: on /cygdrive/d type user (textmode,noumount)
e: on /cygdrive/e type
Paul,
I was able to reproduce your output on Cygwin 1.3.20. The invokation
method (i.e. POSIX vs. mixed path) did not matter, though the DOS line
endings did.
Try invoking your script as
C:/cygtest/testscript 2>&1 | od -c
and look at the result - it should be very informative. I got:
$ c:/cy
n <[EMAIL PROTECTED]>
>Subject: Re: Change in command line behavior between cygwin 1.3.18-1 and
1.3.19-1
>
>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 vers
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,
> 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
Hi,
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 Cygwi
6 matches
Mail list logo
