On 07-Dec-97 Martin Bialasinski wrote:
> I have a programm "xisp" which I use for dialup...
> I added these...lines to my menudefinition:
>
> AddToFunc "connect-xisp"
> + "I" None ["X-ISP"] exec xisp
> + "I" Exec kill -SIGUSR1 `cat /home/martinb/.xisppid`
>
> ...if xisp is not started yet, fvwm will start it and the kill -SIGUSR1
> gets executed too fast.
>
> The function should wait until the windows gets mapped, or something
> similar if I change the startline to start xisp iconic.
Er...you haven't told it to wait for anything. Try adding the
line
+ "I" Wait X-ISP
before the line where you try to signal the process, and it should work
as you want. (Note that the window name is not quoted - quirky, I know,
but it doesn't work if you quote the name.) I just tried this on my
system, and it works fine. Of course, I had to shake off my usual
lethargy and upgrade to the latest version of X-ISP to try this - 2.2
didn't have this feature. :-)
By the way, if you have a working pidof command or the equivalent,
that's probably more reliable than looking at ~/.xisppid. A crashed process
could always leave a stale pid file lying around, and things like this also
tend to be release dependent.
- Bob
--
Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Mon Dec 08 1997 - 20:07:53 GMT