Re: Debug output etc, cluttering the terminal
Emilio Pozuelo Monfort <pochu@debian.org> writes:
> On 18/08/10 11:15, Goswin von Brederlow wrote:
>> The checks
>> in glib seem good enough to handle such cases sanely so maybe the glib
>> could be shut up about them for stable releases (or where users just
>> don't care). Maybe something like setting GLIB_BE_SILENT or so if
>> recompiling the lib silent is out of the question.
>
> No. As you said those are not stupid debug output, but real problems, and should
> be fixed. We're not going to hide them.
>
> Emilio
s/problems/misuse of the lib/
If they are really critical problems then exit(1).
As long as they do not affect the functionality of the app they
aparently will just keep being ignored.
MfG
Goswin
Reply to:
- References:
- Debug output etc, cluttering the terminal
- From: Michael Welle <mwe012008@gmx.net>
- Re: Debug output etc, cluttering the terminal
- From: Neil Williams <codehelp@debian.org>
- Re: Debug output etc, cluttering the terminal
- From: Paul Wise <pabs@debian.org>
- Re: Debug output etc, cluttering the terminal
- From: Michael Welle <mwe012008@gmx.net>
- Re: Debug output etc, cluttering the terminal
- From: Neil Williams <codehelp@debian.org>
- Re: Debug output etc, cluttering the terminal
- From: Wouter Verhelst <wouter@debian.org>
- Re: Debug output etc, cluttering the terminal
- From: Neil Williams <codehelp@debian.org>
- Re: Debug output etc, cluttering the terminal
- From: Ben Hutchings <ben@decadent.org.uk>
- Re: Debug output etc, cluttering the terminal
- From: Goswin von Brederlow <goswin-v-b@web.de>
- Re: Debug output etc, cluttering the terminal
- From: Emilio Pozuelo Monfort <pochu@debian.org>