On 06/21/2017 01:05 PM, Samuel Sieb wrote:
On 06/21/2017 10:53 AM, Mike Wright wrote:
Redirecting to /dev/null doesn't shut them up for me.
Speculating here, but it seems unlikely that GTK is designed for
unsilenceable spewage and is more likely an unwanted gift from the
programmer.
I ended up creating a script, "run", that "exec"s another script, one
that actually invokes the desired GTK loudmouth via another exec. e.g.
"run gimp or run rhythmbox", where gimp and rhythmbox are scripts that
call the executables of the same name. Both scripts redirect 3,2,1
>/dev/null. (Not sure why but a lot of programmers seem to like to
open fd3 while others are partial to 5 & 6.) Mysteriously, the second
script must be executed from its resident directory to get the desired
results (and it's not a case of executing the executable instead of
the script). I have callers for each of the GTK programs I use on a
regular basis.
You're running a graphical application, why do you care what it writes
to the terminal?
Because 90% of my work is CLI. Sometimes I like music, sometimes I have
to do some image manipulation, sometimes I like the news, sometimes I
have to google for things. Not that difficult to imagine.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
