Why Xwin. test works in Xterm and not script? [ Solved ]

[sunburnt]

The file: /tmp/xwin.error is empty when the code is run from a script.
But it works great in Xterm:

Code: Select all

xwininfo -name "$1" 1> /dev/null 2> /tmp/xwin.error

[8-bit]

Routing it through /dev/null basically wipes out the information you are trying to get.

[sunburnt]

No it doesn`t, the only thing being run to null is std. out.
Try it... 2> gets the error but outputs a screen full of info ( 1> ) if there`s no error.
So if the Xwin. title is good 1> sends the Xwin. info to the trash to keep the screen clean.

It`s writing the file every time now, but again... It works fine in Xterm but the script errors.

I took my error message out and now it doesn`t error any more... Weird!
The echo command seems to be the problem, it`s returning back to the function call!
But the if statement should end the script with " exit 7 ;fi" after that! But it never gets there!

[sunburnt]

I solved it...
I moved the test out of that function and put it in it`s own function that`s called normally..

It seems running a function while evaluating it means it evaluates everything as it`s being run,
not just evaluating the returned values as you might expect..

The script works great now... I`ll show what I`m doing in a little bit.