Hello Francois,
On Fri, 14 Dec 2007, Francois Marier wrote:
You should be able to disable the debugging information you don't want to
see by using the kdebugdialog command.
Let me know if you are still having problems. Otherwise, I will mark this
bug as resolved.
(Please take the following with a emotionless distance. There's not a
single line that should make you personally affected ;-)
I *strongly* disagree.
Software should have *sane* defaults. That's not a wishlist. That's a
*must*.
If it weren't that way, then I'd be compiling and assembling all the
software I want and need *by hand*. I don't want to and I won't. That's
just not possible these days any more. That's why I use Debian. Debian
does it for me. I can apt-get install and that's it. I don't have to
figure out and start the gnomeundocumentedobscuretweak program just
because I happen to use the 'pan' or 'gnucash' programms every once in a
year or so. No, I just apt-get them and setup the semantically necessary
stuff and that's it.
And that's the way it should be. Programs should have sane defaults and be
usable right away and not the other way round.
I claim that KDE has had and still has no respect and a very low esteem of
the command line. It might be that for the KDE developers the primary
target of KDE is the users that got the mouse glued to their hand and
can't get it off.
But dumping random stuff to STDOUT/ERR is like shitting on a public
square: neither the public square nor the command line belong to you.
Shitting there stinks and affects random other unrelated actors. It's
very, very unpolite.
(While I write, and this is not made up, some random KDE programm dumps
it's random debug statement to the console, and overwrites the very line
my cursor's in while writing this mail in pine forcing me to save my
mail and restart composing it. 5 seconds before now my mail looked like
this:
I state that ASSERT: "!icon.isEmpty()" in
/tmp/buildd/kdebase-3.5.8.dfsg.1/./libkonq/konq_pixmapprovider.cc (81)
line. It
ASSE
RT: "!icon.isEmpty()" in
/tmp/buildd/kdebase-3.5.8.dfsg.1/./libkonq/konq_pixmapprovider.cc (81)
users that got the mouse
ASSERT: "!icon.isEmpt
y()" in /tmp/buildd/kdebase-3.5.8.dfsg.1/./libkonq/konq_pixmapprovider.cc (81)
ASSERT:
"!icon.isEmpty()"in /tmp/buil
dd/kdebase-3.5.8.dfsg.1/./libkonq/konq_pixmapprovider.cc (81)public
I
claim that KDE has had and still has
a strongASSERT: "!icon.isEmpty()" in
/tmp/buildd/kdebase-3.5.8.dfsg.1/./libkonq/konq_pixmapprovider.cc (81)
line. It ASSERT:
"!icon.isEmpty()" in
/tmp/buildd/kdebase-3.5.8.dfsg.1/./libkonq/konq_pixmapprovider.cc (81) for the KDE
developers t
he primary target of KDE is the
).
So *no*. Please switch it off by default, just like the hundreds of other
instances where KDE feels like dropping stuff to STDERR/OUT without any
pressing need (have you *ever* tried to "startx" KDE from the command
line? Not even a pico second passes and your 80x25 terminal has a seven
lightyears long backlog of KDE debug statements - you have not the
slightest chance to discover whatever sensible in there, in case there is
a *real* problem).
Again. No. Fix the problem. Don't make the users work around it.
Thanks,
*t
--
--------------------------------------------------------
Tomas Pospisek
http://sourcepole.com - Linux & Open Source Solutions
--------------------------------------------------------
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
