On 6 Feb, Mikhael Goikhman wrote:
> AddToFunc LaunchProcessedFvwmScript
> + I ModuleSynchronous FvwmM4 -lock -debug -noread -outfile $[FVWM_USERDIR]/FvwmScript-$0 FvwmScript-$0.m4
> + I Module FvwmScript FvwmScript-$0
>
> AddToFunc StartFunction
> + I LaunchProcessedFvwmScript Calendar
>
> I will try to explain a bit. You need ModuleSynchronous and -lock so that
> the next command running FvwmScript starts only after FvwmM4 is finished.
> You need -debug (not a good name), otherwise the output file specified in
> -outfile is removed after FvwmM4 is finished. You need -noread, otherwise
> the output file is executed by FVWM and we want it for FvwmScript.
Maybe it would be good to change the first function just slightly:
AddToFunc LaunchProcessedFvwmScript
+ I ModuleSynchronous FvwmM4 -lock -debug -noread -outfile $[FVWM_USERDIR]/FvwmScript-$0 FvwmScript-$0.m4
+ I ModuleSynchronous FvwmScript FvwmScript-$0
+ I Exec rm FvwmScript-$0
(delete the M4 output after executing FvwmScript)
Your explanations were great, by the way.
--
Larry Gensch larry.gensch_at_compaq.com
Working for COMPAQ for over a twentieth of a century
--
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 Wed Feb 06 2002 - 09:35:37 GMT