terminal output
Although the output of the murrine rgba thing is quite convenient for customizing .profile, it renders dialog applications like zenity almost useless. Like this:
user@desktop$ echo `zenity --entry` #filled in: blahblah
progname=zenity; RGBA=on blahblah So the usage of zenity in scripting gets screwed unless I go berserk with awk. Feature request: I'm not sure. There is a difference between stdout and stderr, right? Or make some .log file. Or create a verbose / debug switch to be called in .profile. I don't know how difficult it all is, so the right feature choice is up to you.
Thanks a bunch for the rgba stuff by the way; I trusted myself to install that this week and it's really great.
progname=zenity; RGBA=on blahblah So the usage of zenity in scripting gets screwed unless I go berserk with awk. Feature request: I'm not sure. There is a difference between stdout and stderr, right? Or make some .log file. Or create a verbose / debug switch to be called in .profile. I don't know how difficult it all is, so the right feature choice is up to you.
Thanks a bunch for the rgba stuff by the way; I trusted myself to install that this week and it's really great.
? I don't have any output on
I don't have any output on the console... Maybe you're running some custom library, gtk module or so, to enable RGBA stuff.
But then it's not murrine the problem, but you have to ask the author of the gtk module you're using
You're right, sorry, and
Thanks it was in fact very
Post new comment