in message <20030315231204.428b1a5a.groves_ca_at_yahoo.co.uk>, wrote
Timothy Groves thusly...
>
> xterm -e start-rox
>
> and it failed. Then I tried it as:
>
> xterm -e pauseme start-rox
>
> to see if it was throwing out any error messages...and it worked
> perfectly...until I closed the XTerm. Then it vanished. So it
> doesn't seem to out-live the launching XTerm. Though starting it
> in an XTerm, and allowing it to finish starting, then closing the
> XTerm, doesn't seem to kill it. Perhaps the problem's with -e?
Well, i don't know (or care) what rox filer does. If rox filer is
a bona fide GUI, say like xv, gv, etc. or works (or can work) in the
background, like splay or pslatex, then, of course, there is no need
for an xterm. In that case, your script should just work.
If it runs in xterm, then you need something to keep that xterm
alive so that it doesn't die, as you have already found out. And,
this particular issue was resolved in one of comp.unix.* groups.
Let's see... oh yes in comp.unix.shell ...
http://groups.google.com/groups?th=87bb969e4a077afe
- parv
--
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Sun Mar 16 2003 - 01:53:57 GMT