Frank Buss wrote:
>See e.g. http://gcc.gnu.org/ml/gcc-help/2004-01/msg00225.html
>. The effect
>is that when the exe-file is executed by double-click, no
>console-window is created.
Maybe there's a possibility under MS-windows similar to what was available in AmigaOS: the console only appears when I/O is performed, not when the stream is created. So it's open, but not (yet) visible.
It will only appear when the first READ or WRITE is issued. Then it will stay visible.
And BTW, hitting the CLOSE button sends an EOF to the input stream, but not close the window. The window only closes when the stream is closed (well, there are some options, some can disappear and reappear later, like the tiny Linux Konsole/mesg popup).
The EOF condition can be cleared with CLEAR-INPUT. Thus, like on UNIX, one can exit a dozen nested debugger sessions one at a time by hitting the CLOSE button (instead of pressing ^D in a UNIX terminal) a dozen times. When CLISP sees the EOF at top-level it will exit, causing the window to close as well.
It seems such a behaviour could help you: no window, as long as nothing uses it. As soon as your GUI applications uses e.g. *trace-output* (synonym to *terminal-io*), the window appears.
Cute, isn't it?