Christopher,
Thought I'd report back that I just had a chance to try the latest snapshot
(4/22/2001) and the fix you put back works.
typing:
$ MyOwnScript.bat
or
$ MyOwnScript.cmd
both work properly and kick in cmd.exe as expected.
And if I put #!/bin/bash at the top of a .bat or .cmd file, it gets ignored
and does not invoke bash. That's as I would expect.
Thanks for the quick turn on this. Sorry for the delay reporting back, but
wanted to repost as resolved in case others are searching the archives.
Troy
-----Original Message-----
From: Christopher Faylor [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 17, 2001 5:13 PM
To: '[EMAIL PROTECTED]'
Subject: Re: 2001-04-16 DLL not running .bat and .cmd files with cmd.exe
On Tue, Apr 17, 2001 at 02:39:49PM -0400, Larry Hall (RFK Partners, Inc)
wrote:
>At 12:43 PM 4/17/2001, Troy Noble wrote:
>>I installed the 2001-04-16 snapshot DLL, and discovered that
>>now when I type:
>>
>>$ myscript.bat
>>
>>or
>>
>>$ myscript.cmd
>>
>>at a bash prompt, that cmd.exe does not get invoked by
>>default. And of course bash gets confused since it
>>doesn't know what @echo off means ;->
>>
>>Is this expected behavior, or is this broken?
>>
>>of course, I can always type "cmd.exe /c myscript.bat" and
>>that works as expected.
>>
>>I did not re-install any other packages other than just updating
>>the DLL.
>>
>>Thanks, Troy
>
>
>Check the mail archives on this. I believe that Chris Faylor said that
>myscript.bat used to work and is broken now for some reason.
I did say this but I thought I'd fixed it in recent snapshots.
I have just checked in a fix to rectify the problem again. It will be
in tonight's snapshot.
cgf
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
