Add STARTUPINFO-like options to std.process.Child.spawn? about zig

[alexrp]

It would also be worth exposing the flags given to the dwCreationFlags parameter of CreateProcess(). Lots of useful options there for advanced scenarios.

Or even to take a cross-platform struct, something similar to STARTUPINFO ?

Should also look at STARTUPINFOEX here.

[alexrp]

@sensiblearts I still think this should remain open. Exposing the various CreateProcess options is still worthwhile beyond just this particular use case.

[sensiblearts]

Sorry. Reopened.

(Also, after I closed it I noticed that it was added to a milestone!)

[sensiblearts]

@alexrp and @squeek502 , how should I proceed on this? Should I try to get a conversation going with some core maintainers, or should I fork it and take a stab at it myself? I've never requested a change to a std lib.

[JonathanHallstrom]

speaking as an unqualified random person id say just give it a go, whats the worst that could happen?

[sensiblearts]

I guess the worst that could happen is that I waste a lot of time going in the wrong direction. I'm getting old :-)

[sensiblearts]

I found a workaround that may in the end be better. My goal is to minimize a spawned child process terminal.

On Windows, I can use cmd.exe's start command, which can take a /min param; e.g., instead of spawning a NodeJS process directly, I write a .bat file and spawn/run it. The .bat file:
start "NJNODE" /min node ./index.js

I don't need a handle to the process to kill it, because it is named ("NJNODE"); instead, to kill it, I run another batch file:
taskkill /FI "WindowTitle eq NJNODE*" /T /F

I'm pretty sure I can accomplish something similar on posix systems, using nohup or tmux.