On 21 Jun 2002 12:07:26 +0100, Tony Finch wrote: > > The fvwm manual notes the potential for race conditions when using the > Exec command, and I stumbled across this recently when trying to put more > of my X startup under fvwm's control (the xrdb command didn't complete > before xclock started). So I added an ExecWait command for running > programs synchronously. It's OK as it is for short-lived programs, but > for use with longer-lived things it needs support for the EscapeFunc > mechanism.
I am not sure. PipeRead already does exactly this and even more. "ExecWait something" is equivalant to "PipeRead `something >/dev/null'" The name ExecWait may be confused with a combination of 2 commands (that are often used for commands launching windows): Exec something Wait somepattern Maybe BlockingExec is a better name. Regards, Mikhael. -- Visit the official FVWM web page at <URL:http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
