winemenubuilder: disable debug output for .desktop files
austinenglish at gmail.com
Fri Apr 3 15:43:56 CDT 2009
On Fri, Apr 3, 2009 at 3:38 PM, Vincent Povirk
<madewokherd+8cd9 at gmail.com> wrote:
> On Fri, Apr 3, 2009 at 3:29 PM, Austin English <austinenglish at gmail.com> wrote:
>> Several games experience this problem, but it's difficult to use the
>> quiet fixme approach, since they have variable information. Converting
>> the fixme's to trace's/warn's may be a viable option.
> What if we abandoned "print FIXME the first time, print nothing
> subsequent times" in favor of "print FIXME the first time, print
> WARN|TRACE subsequent times"?
> I've personally lost some useful information in a debug log because of
> the "FIXME once" idiom. I was explicitly asking for the gdiplus
> channel and expected to see all the calls.
> A FIXME_ONCE macro could be written fairly easily that does this
> efficiently (i.e. without writing the same code twice).
I think that would be very useful, and would love to see that.
However, that's a separate issue from disabling output for .desktop
files. I don't see many (any?) use cases where having that output when
launched from a gui is useful.
More information about the wine-devel