On 06 Feb 2002 15:31:54 +0100, Pier Paolo Glave wrote:
>
> I'd be interested in using FvwmM4 to pre-process FvwmScript files.
> I've read in the man pages that the "-noread" option is useful in these
> cases, but I had no success...
Suppose, you have a file named FvwmScript-Calendar.m4 in ~/.fvwm/ or
/usr/local/share/fvwm (or whatever `fvwm-config --fvwm-datadir` returns).
This function does what you want in 2.4.x.
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.
Regards,
Mikhael.
--
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:12:27 GMT