The Grumpy Editor's guide to personal finance managers (Part I)
The Grumpy Editor's guide to personal finance managers (Part I)
Posted Sep 13, 2005 21:04 UTC (Tue) by foo@share-foo.com (guest, #7940)Parent article: The Grumpy Editor's guide to personal finance managers (Part I)
KMyMoney starts in the usual manner for KDE applications - slowly, and with a lot of strange stuff written to the standard output.
STDOUT? What's that? Everyone knows that KDE apps are supposed to be started from the the big K menu.
Posted Sep 13, 2005 21:21 UTC (Tue)
by Ross (guest, #4065)
[Link] (1 responses)
Posted Sep 13, 2005 23:11 UTC (Tue)
by pynm0001 (guest, #18379)
[Link]
Posted Sep 13, 2005 21:44 UTC (Tue)
by atai (subscriber, #10977)
[Link] (5 responses)
Posted Sep 13, 2005 22:19 UTC (Tue)
by hawk (subscriber, #3195)
[Link] (3 responses)
Posted Sep 14, 2005 0:29 UTC (Wed)
by dlang (guest, #313)
[Link] (1 responses)
Posted Sep 14, 2005 21:25 UTC (Wed)
by tzafrir (subscriber, #11501)
[Link]
Posted Sep 23, 2005 7:03 UTC (Fri)
by rqosa (subscriber, #24136)
[Link]
Posted Sep 13, 2005 23:55 UTC (Tue)
by bk (guest, #25617)
[Link]
Posted Sep 13, 2005 22:44 UTC (Tue)
by danielthaler (guest, #24764)
[Link] (1 responses)
Posted Sep 14, 2005 13:58 UTC (Wed)
by nix (subscriber, #2304)
[Link]
What's really annoying is that they continue to write to stdout when they are backgrounded or even after they exit. I guess they fork some other process which does the writing... seems like a bug to me.The Grumpy Editor's guide to personal finance managers (Part I)
This should only occur for applications which are designed to be unique The Grumpy Editor's guide to personal finance managers (Part I)
(that is, only one running instance at a time), as a side-effect of the
implementation.
And they don't write to stdout after exit, that's the rest of KDE, the
things like running kioslaves and the DCOP server for example.
Does KDE applications write more messages to stout than gtk+/GNOME applications?The Grumpy Editor's guide to personal finance managers (Part I)
I don't know about that, but most GNOME/GTK applications don't write anything to stdout. (I know of at least one exception, though.)The Grumpy Editor's guide to personal finance managers (Part I)
firefox sure dumps a lot of stuff out to the terminal (I don't know if that is the one exception you were thinking of, but I don't run many other gnome/gtk programs)The Grumpy Editor's guide to personal finance managers (Part I)
At least in Debian its output is thus redirected to /dev/nullThe Grumpy Editor's guide to personal finance managers (Part I)
If I remember correctly, the version of Sylpheed that was in Debian Woody
would write things to the terminal.
The Grumpy Editor's guide to personal finance managers (Part I)
Yes. I use GNOME but start most programs from an xterm (well, gnome-terminal) and GTK2 programs are almost always polite. KDE programs, OTOH, spew lots of crap which render the terminal useless until the KDE program is killed.The Grumpy Editor's guide to personal finance managers (Part I)
Usually you can significantly reduce the amount of output from kde apps by running "kdebugdialog" and deselecting everything to turn off information output to STDOUT.The Grumpy Editor's guide to personal finance managers (Part I)
If you run "kdebugdialog --fullmode" you can turn off warnings and errors too.
Also by compiling them with --disable-debug, which is *not* the default.The Grumpy Editor's guide to personal finance managers (Part I)