SUMMARY

Linux is known of programs working in standard manner:

      - Normal message to stdoout
      - Error messages to stdout

The debug messages are not displayed, unless specifically enabled via:

	- Command line options (-d, --debug or similar)
	- Environment variables (PROGRAM_DEBUG=1, or similar)
	- UI (Menu -> Debug, or similar)

By always sending output to the screen causes multiple problems:

   	- Programm differes from the rest of the 99.99% utilities in Linux.
	- It gaves wrong impression: does this program have problems?
	- It's makes it harder to tell good messages from bad
	- It causes havoc on 3rd party programs (see below)
	- It requires doing "extra hoops"
	  * In scripts
	  * In command line

Please suppress debug messages by default, enable only when requested.

DESCRIPTION

For some reason kfmclient sends debug messages in normal use. An
example

  konqueror &
  kfmclient newTab /usr/local

    kfmclient(17331) ClientApp::doIt: Creating ClientApp
    Qt: Session management error: None of the authentication protocols specified are supported
    kfmclient(17331) ClientApp::createNewWindow: KUrl("file:///usr/local") mimetype= ""

This may not look a problem, but it causes wrecking the UI in 3rd
party applications. Am example:

    1. Configure Emacs, Gnus and connect to group gmane.linux.debian.devel.*
    2. Configure Emacs to browse URLs in konqueror
    3. In Gnus news reader interface reading artile, click on URL at
       *Article* buffer

    => The article content (or any buffer in that matter) is wrecked by
    inserting the response from the kfmclient

This is how the output was inserted into an artile. See lined marked
with "*" to the left. The problem is even worse in *Summary* buffer
where the whole threading of messages goes beserk due to these
messages.

FYI, related to this bug, there was discussion in Debian devel mailing
list about the use of debug essages by default.

http://news.gmane.org/find-root.php?message_id=%3c20100815102052.GD397%40codelibre.net%3e

    From: Roger Leigh <rleigh <at> codelibre.net>
    Subject: Re: Debug output etc, cluttering the terminal
    Newsgroups: gmane.linux.debian.devel.general
    Date: 2010-08-15 10:20:52

    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.

    (...) 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

FYI, related to this bug, there was discussion in Debian devel mailing
list about the use of debug essages by default.

http://news.gmane.org/find-root.php?message_id=%3c20100815102052.GD397%40codelibre.net%3e

    From: Roger Leigh <rleigh <at> codelibre.net>
    Subject: Re: Debug output etc, cluttering the terminal
    Newsgroups: gmane.linux.debian.devel.general
    Date: 2010-08-15 10:20:52

    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.

    (...) 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