What is it with X applications spewing debug messages, errors, warnings and general information to the console?
I'm a FOSS user and have been for a little over 12 years now and; while I understand the need for the output of debug messages, errors, warnings and general information; isn't it about time for developers to write code that allows users/vendors to disable the code statements responsible for console output at compile time or at least make the application silent by default?
I ask this question because I just compiled Miro for my Gentoo box and was having problems with it. I ran tail against my .xsession-errors file to see if I could find the problem while starting Miro. However; I run KDE, which likes to spew massive amounts of debug messages, errors, warnings and general information to the console, and could not read Miro's console output via tail because of KDE's spewage.
Now granted, I could of started Miro from a terminal session and read its console output right there in the terminal session but, if KDE wasn't spewing to the console, I could of read Miro's output from the .xsession-errors file.
Also, I wonder how much resources are being taken up by X applications printing to the console, especially the different desktop environments or other heavyweights like Evolution or OpenOffice, and how much quicker applications would run if they didn't have the code statements responsible for console output in them?
Saturday, February 16, 2008
Subscribe to:
Comments (Atom)