"Larry Hall (RFK Partners, Inc)" wrote:
>
> At 01:50 PM 1/15/2001, Earnie Boyd wrote:
> >
> >Create a noop program named #!.exe and put it in command.com/cmd.exe
> >PATH.
> >Then at the top of your .bat file put
> > #! c:\\path\\to\\cmd.exe /c
> >and this will cause Cygwin to think it's executable and execute it.
> >
>
> Right but these batch files won't run from cmd.exe/command.com like this
> though. Still, its a way to "convert" batch files to run under the Cygwin
> shells if you don't need them to run under cmd.exe/command.com anymore.
>
Huh. Of course they will continue to work under cmd.exe/command.com, if
not, they wouldn't work under Cygwin shells either. It's the reason you
create a noop program named `#!.exe'. The cmd.exe/command.com shells
actually execute the program which does nothing more than return 0.
>
> The reason I directed the poster to the email archives is I seem to
> remember that there was also some way to get bash/sh to run batch files
> directly, without invoking the cmd.exe/command.com explicitly (i.e. one
> could just type b.bat at the sh/bash prompt). I don't remember the details
> though (which is the part that would be in the email archives for those
> interested in looking!;-)) And actually, for me, this works. YMMV and
> don't ask me why it works for me!;-)
>
Well, I certainly don't remember anything beyond what you suggested. I
have posted my #!.exe noop program solution before, but it's been a
while so I thought it was time to repeat myself.
Cheers,
Earnie.
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
