Alle Saturday 12 April 2003 16:17, Dan Espen ha scritto: > Ploum <[EMAIL PROTECTED]> writes: > > > See this thread: > > > > > > http://www.mail-archive.com/fvwm@hpc.uh.edu/msg03150.html > > > > > > Try: > > > > > > Exec nohup rox > > > > I try it. > > > > It's better because it works if another rox window is open. > > If not, nothing happens ! What's the deal with this software ? > > I haven't looked at the source code, but I believe its > trying to figure out if its invoked from a tty. > > Maybe you should contact the author.
(sorry for the late reply) I asked to the rox mailing list. They say that the problem is probably due to the fact that Fvwm closes stdin in the Exec and later rox tries to divert it to /dev/null. They suggest that Fvwm should do something similar instead of closing stdin directly. -- 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 [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
