On 09-Dec-97 Martin Bialasinski wrote:
> I tried "Wait". This doesn't do what I want. Imagine this case...
Ok, I'm a little dense. Now I see what the problem is - I thought
it was just the timing between starting X-IXP and trying to send it a signal.
Handling the case where X-IXP is already active is a job for a shell script,
really. But it's not a very complicated one - check to see if the xisp
process is active, exec xisp if it isn't and do a check-process/sleep
loop until it looks active, then send the signal. A lot can be done with
FVWM functions, but fvwm is a window manager, not a full-fledged
programming language - nor was it meant to be. For that, you'd need some-
thing like GWM. :-)
Alternatively, two menu items and functions could be used - one for
when X-ISP is active, one for when it's not.
> Where do I get such "pidof" utility from? I don't have one and it sounds
> as is I really should have one :-)
It's part of the sysvinit package for Linux systems. (pidof is
actually a symlink to killall5, in the /sbin directory.) If you're using
Debian Linux, I would think it would be installed as part of the base system.
But this is straying a bit off the subject of FVWM.... If we continue in
this vein, we should probably take it off-line from the mailing list.
Cheers,
- 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 Tue Dec 09 1997 - 21:11:34 GMT