Just for fun, click up a terminal and run
kwrite aa &
hit a few keys in the editor screen, carriage return, repeat,...

Note all the console messages.

Want to know how to disable those messages? Run
kdebugdialog
and play around.

Would anyone with a KDE.org membership/account please make a
recommendation/suggestion that programs should have a preference to
dis/enable debugging output. Default setting, off.


My solution for new installs is to restore
$HOME/.kde4/share/config/kdebugrc
after disabling about 23 dialog groups.

On Thu, 15 Oct 2009 14:20:57 +1100, Doug Laidlaw wrote:


Instead of an alias I made a wrapper.

#************************************* start kwrite ****************************
#*
#* kwrite - suppress kde dialog messages when using kwrite
#*
#* Note: /local/bin/kdebugrc_kwrite controls messages and is created
#* by running kdebugdialog and moving $HOME/.kde4/share/config/kdebugrc
#* to /local/bin/kdebugrc_kwrite
#*
#*******************************************************************************

_dir=$HOME/.kde4/share/config
_fn=$_dir/kdebugrc

if [ -d $_dir ] ; then
if [ -e $_fn ] ; then
/bin/mv ${_fn} ${_fn}_tmp
fi

ln -s /local/bin/kdebugrc_kwrite $_fn

fi # end [ -d $_dir ]

/usr/bin/kwrite "$*" &

if [ -e $_fn ] ; then
sleep 2
/bin/rm -f {_fn}

if [ -e ${_fn}_tmp ] ; then
mv ${_fn}_tmp {_fn}
fi
fi

#************************************* end kwrite ******************************





After some research I found the culprit.



Not their fault, it is Mandriva's.



Yep, been there.



Yes, that is correct.

Current KDE setup is, if you have not changed something, you will not
have a $HOME/.kde4/share/config/ file.


You should also have a /usr/share/config/kdebugrc, at least for kde4


And that is the culprit in this who done it.

I still say the dialog control should be in an application's preference.

Bit Twister wrote:


To get around that one, I made kwrite an alias to "kwrite $1 2> /dev/null"
but even running "/usr/bin/kwrite" which should bypass the alias, I see no
messages now. I tried using a non-KDE terminal, but that didn't help at
all. Apparently, KDE still want to advertise their incompetence, such as:
"QPainter isn't running, but it can't find this -- or this -- or this."

My personal opinion is that those messages are for developers, and the whole
lot should be turned off by default for the ordinary user. Probably the
only developers who have any use for them are KDE's. They will exist under
Windows (although on the rare occasions when I have used a command box, I
have never seen one) and if we run Linux as KDE wants, as another Windows,
we won't see them. Everything still runs fine without them.

What peeves me is something like this:

I will exit a program started from a terminal, and wait for the drivel to
stop. Then I start typing my next command. Half-way through the typing,
KDE interposes a late message, and I need to remember where I was. The
message about ICE used to be the main offender.

I don't have $HOME/.kde4/share/config/kdebugrc I have kdebugrc in
/opt/kde3/share/config/ (with 'example' mis-spelled,) and in
/var/lib/mandriva/kde4-profiles/common/share/config/ (spelled correctly, and
a lot more detailed.) I don't understand it a bit.

Doug.

On Thu, 15 Oct 2009 12:26:01 +0100, Grimble wrote:


Hmmm, that "thingy" can increase error messages. It is not going to
make kwrite run.

I just fired up 2009.1 kwrite in virtual box without problem.

All updates applied. Looking around it seems kde is 4.2.4 not 4.3.2.

Going to guess you have a hybrid problem running new kde on top of an
old install.

Looking in the menu editor, the 2010.0 kde 4.3.2 kwrite command is
kwrite %U

Bit Twister wrote:

Well at least kwrite starts up from the command line. If I start it from
the
application launcher menu, it crashes before a editor screen appears
(error message:
Application: KWrite (kdeinit4), signal: Aborted
[Current thread is 0 (process 2492)]
I'll try the kdebugdialog thingy.
Grimble

Bit Twister wrote:

Grimble

On Wed, 14 Oct 2009 12:33:10 -0400, Bit Twister wrote:

Quote:

Want to know how to disable those messages? Run
kdebugdialog

Thank you for this. That's one I hadn't seen. Also, run
/opt/kde3/bin/kdebugdialog for the applications that haven't been
ported to kde4.

I've turned off all of the debug output for both, and really notice
the difference.

Regards, Dave Hodgins

--
Change nomail.afraid.org to ody.ca to reply by email.
(nomail.afraid.org has been set up specifically for
use in usenet. Feel free to use it yourself.)

On Tue, 03 Nov 2009 14:16:41 +0000, Maurice Batey wrote:

Hmmm, I do not believe kdebugdialog has a selection for any app
regardless of release.

I was just indicating how you can turn off messages when using kwrite.

Since other apps could have the same "Feature" I wrote a wrapper to
copy a kdebugrc into kde*/share/config, launch the app, sleep, then
delete kdebugrc. That allows the ability of messages to
show up from some other app while still using a noisy app.

On Sun, 18 Oct 2009 03:26:26 -0400, David W. Hodgins wrote:


Me neither - thanks, BT!

But kdebugdialog doesn't list 'kwrite' here. (2009.1).

--
/\/\aurice
(Replace "nomail.afraid" by "bcs" to reply by email)