|
From: Bastian E. <ba...@ei...> - 2010-02-09 22:36:41
|
> So, to be clear, if I mark 0launch as a GUI application that doesn't > need a terminal, and I explicitly open a terminal window myself and > run "0launch --console" then what happens? If you run a GUI application from a terminal window it will not be connected to that terminal in any way. The shell in the terminal will return immediately after launching the GUI application and request new input (running the GUI application asynchronously), whereas a non-GUI application would have replaced the shell (synchronously). > I'd expect its output to come to the existing terminal window. Are you > saying that Windows would explicitly close its streams in this case? Windows doesn't close the streams of the terminal, the GUI application just doesn't inherit them. Windows basically forces each type of application to always stay in its own realm. Non-GUI apps are always associated with a terminal window, which they might inherit when launched from within another non-GUI application or spawn when launched from a GUI application. GUI apps always stay detached from any kind of Terminal. |