GUI applications writing garbage to stdout/stderr

[Zbigniew Jędrzejewski-Szmek]

On Thu, Jan 15, 2015 at 12:35:02AM +0100, Reindl Harald wrote:
> 
> Am 15.01.2015 um 00:29 schrieb Alexander Ploumistos:
> >On Thu, Jan 15, 2015 at 1:16 AM, Björn Persson <Bjorn at rombobjörn.se
> ><mailto:Bjorn at rombobjörn.se>> wrote:
> >
> >    If they don't have such a build-time option, then what I'm saying is
> >    that if one were to suppress the messages, then one should do it with a
> >    run-time option, not a build-time option. Then no different build would
> >    be needed and debugging would be easy.
> >
> >No argument from me there. I just hate it when things start dying and
> >leave you clueless (without as much as a -v option). And let's not
> >forget that a special debug build may not suffer from the same issues as
> >the "regular" one. It has happened to me on occasion.
> >Perhaps over the years I've grown accustomed to the gibberish in my
> >terminal and started considering it normal, instead of buggy, as Reindl
> >Harald points out
> 
> the real problem with that crap messages is that if you are about
> writing a longer command line and the in background mode started GUI
> app decides to blow out it's helpful messages they appear unasked in
> the middle of your input and so the only thing you can do is CTRL+C
> and hope the next try don't get interrupted again
^L should work.

Zbyszek