Hello Alex. Thanks for your response. On Fri, Apr 29, 2022 at 9:34 AM brainman <alex.brain...@gmail.com> wrote:
> Once windows executable is built, go has no control over how this program > executes. > > When command line program is executed by clicking in explorer window > Windows automatically starts a new console window and the console is used > for stdout output (I did not check that). If command line program is > started from existing cmd.exe console, new process just uses the same > console. > > When you click on GUI executable in Windows explorer, no console windows > is started (I did not check that). Same for GUI executable started from > cmd.exe console - new GUI process is not attached to parent console (I did > not check that). > Right. So I have a GUI executable that might be launched from a console but it will not be "attached" to that parent console. Is there a way to attach the GUI executable to the parent console, perhaps using a Windows system call? -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/CAPmHGLNS1QMVKqHrjoLskEy1SFhCYXc_Ra%2BnEiysHoA%3DV7Fw2A%40mail.gmail.com.
