On Oct 24, 2014, at 7:57 AM, Eric Blake <ebl...@redhat.com> wrote: > On 10/24/2014 07:53 AM, Corinna Vinschen wrote: >> On Oct 24 06:05, John Wiersba wrote: >>> I would have thought cygwin1.dll contains the code necessary to do this, >>> like the linux kernel does. >> >> run.exe doesn't start the executable via a Cygwin function, but via a >> Windows call. There's no chance for the DLL to handle shebangs. > > Of course, if you wanted to be nice, you could write a patch to run.exe > that teaches it to read() the contents of a file that it is about to > execute, and if it starts with a shebang…
I get that run.exe must do low-level Win32 API things in order to suppress the console window, which is why it is currently a native app, rather than a Cygwin app, but I don’t like the idea of reinventing execve(2) inside run.exe. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
