On Mon, Apr 6, 2009 at 3:48 AM, wrote:
> Hi,
>
> Austin English wrote:
>>> I don't think it's safe to assume that stderr will be lost if the
>>> program was started from a .desktop file.
>>The majority of users are double clicking .desktop files to start
>>their applications. Where do you see std
Hi,
Austin English wrote:
>> I don't think it's safe to assume that stderr will be lost if the
>> program was started from a .desktop file.
>The majority of users are double clicking .desktop files to start
>their applications. Where do you see stderr going to in this case?
It is centralised to $
On Sat, Apr 4, 2009 at 1:37 PM, Warren Dumortier wrote:
> I just responded to my previous mail, nice to see you care about that issue!
>
> I just want to say that nobody uses the desktop file to launch a program to
> debug, i think, in response to previous messages. That would be very nice.
>
> Is
I just responded to my previous mail, nice to see you care about that issue!
I just want to say that nobody uses the desktop file to launch a program to
debug, i think, in response to previous messages. That would be very nice.
Is it difficult to implement? Why not simply add WINEDEBUG-all to gen
On Fri, Apr 3, 2009 at 4:05 PM, Vincent Povirk
wrote:
> I'll work on a patch for the FIXME thing.
Turns out this is not "fairly easy" but actually "incredibly
difficult". We have a fallback case at
http://source.winehq.org/source/include/wine/debug.h#L133 with a macro
that returns a statement tha
You forgot to CC wine-devel in your original e-mail:
On Fri, Apr 3, 2009 at 4:05 PM, Vincent Povirk
wrote:
> On Fri, Apr 3, 2009 at 3:43 PM, Austin English
> wrote:
>> However, that's a separate issue from disabling output for .desktop
>> files. I don't see many (any?) use cases where having th
On Fri, Apr 3, 2009 at 4:09 PM, Austin English wrote:
> Why couldn't you simply use a second WINEDEBUG="fixme+all,err+all" to
> override the variable in the .desktop file?
The command is "env WINEPREFIX="..." WINEDEBUG=-all ...". No matter
what I set WINEDEBUG to when I start that, wine will see
On Fri, Apr 3, 2009 at 3:38 PM, Vincent Povirk
wrote:
> On Fri, Apr 3, 2009 at 3:29 PM, Austin English
> 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 b
On Fri, Apr 3, 2009 at 3:29 PM, Austin English 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
On Fri, Apr 3, 2009 at 3:19 PM, Vincent Povirk
wrote:
> I'm not sure if this is a good idea.
>
> I don't think it's safe to assume that stderr will be lost if the
> program was started from a .desktop file.
The majority of users are double clicking .desktop files to start
their applications. Wher
I'm not sure if this is a good idea.
I don't think it's safe to assume that stderr will be lost if the
program was started from a .desktop file.
If default debug output slows anything down noticeably, that should
probably be fixed.
Vincent Povirk
On Fri, Apr 3, 2009 at 2:40 PM, Austin English
11 matches
Mail list logo
