ok. I didn't realize that oocalc actually executed in your first attempt.
Out of ideas then.
FWIW - a few guesses: I'd execute oocalc under strace, and try to find
what is killing oocalc (does it decide to exit, or is it sent some
signal). If your suspecting xterm to be the culprit (i.e., yr script
works-as-expected w/o the xterm wrap) then maybe it'll be worthwhile
looking into the X resources yr xterm is reading.
HTH
Amit
Mick wrote:
On Tuesday 16 March 2010 07:40:04 Amit Dor-Shifer wrote:
What does
xterm -fg green -bg black -e 'gpg Personal/data.ods.gpg;echo $?' tell you?
It doesn't return anything on the terminal I launch it from, but decrypts the
file in an xterm and then closes it (the xterm). So the gpg part works fine.
I'm thinking that gpg fails, so oocalc never launches (because you
conditioned its execution with '&&', and the script continues to shred the
file.
The gpg part does not fail, because when I run:
xterm -fg green -bg black -e 'gpg Personal/data.ods.gpg && oocalc \
Personal/data.ods'
An xterm opens up asks for a passwd to decrypt the file, decrypts it and
launches OOo. However, the xterm dies immediately after that.
On my x86 machine, the xterm stays open until I close OOo. This is how it
should work; i.e. the xterm should continue to run as long as any processes
within it are still running.
This makes me think that it may be some env or profile difference ...? What
would control this behaviour in an xterm?
