http://bugs.winehq.org/show_bug.cgi?id=34730
--- Comment #1 from Jason Edmeades us@edmeades.me.uk 2013-11-04 15:26:51 CST --- What is the use case for doing this? Obviously you cannot do this on windows, and reading the code and the change I made, it was purely by luck that it ever worked in wine's command anyway. In fact it didnt really work - if you try it, you'll see that it runs the unix program without waiting for it to complete, and gives you the command prompt back which is then overwritten by the programs output.
If you assume the thing being run is a fully qualified unix path, its relatively easy to get this functionality back, I guess the question is whether we *should* add back in the functionality as there's little that can be done about the limitations.
Attached is patch to get it working, but not sure it would be accepted if I submit it. It only supports a command in the form /path/to/unixexecutable