Tor Lillqvist <[EMAIL PROTECTED]> writes:
> I guess there is a mismatch in the ways of thinking here: GIMP thinks
> that writing to stdout means the output will mostly go somewhere where
> the user doens't see it, unless he explicitly does something unusual
> (starts GIMP from the command line).
> The Win32 code in GLib again thinks that g_print() etc messages are
> *important*, and supposed to be shown to the user in some way, even
> opening a new console window if there isn't one already. If the user
> wants to redirect stdout and stderr (to NUL: or a file), he can do it
> from the command line.
There got to be a way to change this behaviour of g_print(), no?
Gimp-developer mailing list