On Wednesday 17 March 2010 22:57:41 you wrote: > On Wednesday 17 March 2010 09:15:17 Amit Dor-Shifer wrote: > > 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.
I'm posting this to the list on behalf of Jack, because his posts don't make it to the list for some reason: ============================================ You didn't see it in the list because it hasn't shown up there yet, despite three tries to post..... What I mean is that if I type "oocalc somefile" in a term (it doesn't seem to matter xterm, konsole, ...) I almost immediately get the next shell prompt, even before the oocalc (or oodraw or oowrite) window is fully displayed and ready to work. It does not smell to me like anything to do with the terminal program, or even the shell, although there may well be an environment variable that OO is checking. oowriter --help (and any variation I have tried) seems to ignore the request for help. If you look at the ooffice help on command line parameters, there is a note about gentoo having a custom version - but I haven't been able to find anything at the gentoo site either. I have not yet tried launching from a script in case that behaves any differently. Note that since the shell has given the next prompt - the terminal will certainly think everything is done, and happily close if the script is finished. The trick will be to explicitly find a way to check that oo has finished. If you just launch oo from a command line in a terminal, do you get the next shell prompt immediately, or not until you exit oo? Jack ============================================ Thanks Jack, this is rather interesting: On two machines including the amd64 laptop the terminal exits immediately, while the OOo is being launched. Both of these have OOo compiled from source. The third machine (an old x86 laptop) has the OOo binary installed. The binary installation behaves as I thought was the norm, i.e. the terminal does not exit, but remains open until I close OOo. So this problem that reported I guess is due to a difference between the two types of OOo, built from source or binary. I looked at the CLI help options by running 'ooffice -help'but I can't see anything in there that will change this behaviour on the OOo built from sources. Any other ideas? -- Regards, Mick
signature.asc
Description: This is a digitally signed message part.
