Process.execute opens new console

The issue is that you are starting console applications, and the OS allocates a console for you if there is not one already. If you are starting GUI applications the console should not appear. This is consistent with starting a console application from Explorer, and is considered to be default behavior. Having a window pop up is cosmetic, not being able to redirect output is loss of functionality.

I have not tried the CREATE_NO_WINDOW flag, but I cannot tell from the documentation that it is any different from DETACHED_PROCESS. I looked at the documentation and researched online for a while to figure out if it was any different. I will try it out to see if it helps.

I'm looking at enhancing process to be able to specify whether stdout/stderr/stdin should be redirected, perhaps we could include a no_window flag that does nothing on posix systems?

The ehancement proposal for optionally redirecting output is #718

I tried reading the stdout of a batch file when using DETACHED_PROCESS, and it works for me. I also did some tests with CREATE_NO_WINDOW, but I couldn't see any differences from using DETACHED_PROCESS. Batch files and exes work just fine in both cases. With zero for the flag, console windows are created for both batch files and exes, when run from a subsystem:windows app.

I only tried stdout, not stderr or stdin. I didn't use tango, but regan heath's stuff and phobos. Should work the same, though.

Hm.. did you try running a console-based process in that batch file? My test was a batch file that runs diskpart /?, and I did not get output from stdout.

(In [3237]) Changed flag for creating process to CREATE_NO_WINDOW, which appears to have the best of both worlds (does not flash a console window, and allows redirection of stdout/err for batch files).

This flag isn't supported on Windows 95/98/Me, but I don't think that really matters much these days.

fixes #933