On Sun, Aug 15, 2010 at 10:02:15AM +0100, Neil Williams wrote: > On Sun, 15 Aug 2010 12:44:59 +0800 > Paul Wise <firstname.lastname@example.org> wrote: > > > On Sun, Aug 15, 2010 at 7:09 AM, Neil Williams <email@example.com> > > wrote: > > > > > It's not clutter. If you don't want to see it, run the command and > > > redirect stderr. > > > > debug output should certainly not be output by default in released > > versions without a command-line or configuration option turning it on. > > On the contrary, I've outlined some situations where on-by-default is > the best way to identify the bug itself. If you're not specifically debugging, it's useless noise that masks more important stuff. Just add a --debug option or a DEBUG environment variable and you then have a well-behaved program rather than one which spews irrelevant crap all over your work. This is a beef I have with all KDE-based programs, as well a a large number of GTK+-based programs. These messages add zero value, and should not be enabled in a production release--their developers should have noticed and fixed them prior to release. In most cases they aren't even debugging output--they are pointless chatter that noone except the developers would care about. Regards, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linux http://people.debian.org/~rleigh/ `. `' Printing on GNU/Linux? http://gutenprint.sourceforge.net/ `- GPG Public Key: 0x25BFB848 Please GPG sign your mail.
Description: Digital signature