https://bugs.winehq.org/show_bug.cgi?id=34730
--- Comment #23 from Alexandre Julliard julliard@winehq.org --- (In reply to Emmanuel Charpentier from comment #22)
Maybe we should have an utility calling the system (Linux) shell and associate it with, for example the ".SH" exytension ? This would allow to create specific or generic shells invoking whatever Linux progfram we wish and communicate its outputs to Wine ?
If your script ends in .exe, you should be able to run it directly from the command line.
If it ends in .sh, you have to add ".sh" to PATHEXT, and then it should run fine.
If it has no extension, adding "." to PATHEXT should have the same result.
As far as I can tell, this is exactly how Windows behaves. Do you see a different behavior?
Note: start /unix uses a different code path, and probably behaves differently. This should be a separate bug, this bug is about cmd.