Am 15.01.2015 um 00:36 schrieb Zbigniew Jędrzejewski-Szmek:
> 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
which clears also the screen - bad if the input you make depends on the
output of previous commands, the same if your foreground terminal app is
producing output intended for copy&paste into a mail after finish
a application has *no* valid reason to spit debug output left and right
unasked, and as said proven by deprecation warnings over years even the
upstream developers don't read them - so why annoy endusers