http://bugs.winehq.org/show_bug.cgi?id=10324
--- Comment #6 from Austin English austinenglish@gmail.com 2007-11-06 14:25:10 --- Would seem to me that on some programs that have a lot of output, the warning may get lost in the terminal and never seen, thus defeating the whole point of the warning. Sort of how many users never see warnings to fix their sound settings/etc, then go on to report a bug that is soon after closed invalid. Just my $.02.
As for supporting environmental variables/registry setting, I don't see a reason we can't have both.