The fvwm m4 pre-processor
Module FvwmM4 [options] filename
The FvwmM4 module can only be invoked by fvwm. Command line invocation of the FvwmM4 module will not work.
When fvwm executes the FvwmM4 module, FvwmM4 invokes the M4 pre-processor on the file specified in its invocation, then FvwmM4 causes fvwm to execute the commands in the resulting file.
FvwmM4 can be invoked as a module using an fvwm command, from the .fvwm2rc file, a menu, mousebinding, or any of the many other ways fvwm commands can be issued.
If the user wants his entire .fvwm2rc file pre-processed with FvwmM4, then fvwm should be invoked as:
fvwm -cmd "Module FvwmM4 .fvwm2rc"
Note that the argument to the option "-cmd" should be enclosed in quotes, and no other quoting should be used.
When FvwmM4 runs as a module, it runs asynchronously from fvwm. If FvwmM4 is invoked from the .fvwm2rc, the commands generated by FvwmM4 may or may not be executed by the time fvwm processes the next command in the .fvwm2rc. Invoke FvwmM4 this way for synchronous execution:
ModuleSynchronous FvwmM4 -lock filename
Some options can be specified following the modulename:
I think this makes all the m4 directives require the prefix "m4_".
Causes built-in defines to be prefixed with "m4_" (i.e., m4_HOME is defined instead of HOME, etc.)
Lets you pass an option to the m4 program. Not really needed as any unknown options will be passed on automatically.
Lets you change the m4 start-of-quote character to character.
Lets you change the m4 end-of-quote character to character.
Instead of invoking "m4", fvwm will invoke name.
Instead of creating a random unique name for the temporary file for the preprocessed rc file, this option specifies the name of the temporary file created. FvwmM4 attempts to remove this file before writing to it, so don't point it at anything important even if it has read-only protection.
Causes the temporary file created by m4 to be retained. This file is usually called "/tmp/fvwmrcXXXXXX"
If you want to use this option you need to start FvwmM4 with ModuleSynchronous. This option causes fvwm to wait that the pre-process to finish and then FvwmM4 asks fvwm to Read the pre-processed file before continuing. This can be useful at startup if you use a session manager like Gnome. Also, this is useful if you want to process and run a Form in an fvwm function.
Causes the pre-processed file to be not read by fvwm. Useful for pre-processing an FvwmScript script.
FvwmM4 defines some values for use in the pre-processor file:
Always set to "fvwm".
The name of the machine running the X Server.
The name of the machine running fvwm.
The hostname of the machine running fvwm. Generally the same as CLIENTHOST.
The operating system for CLIENTHOST.
The name of the person running fvwm.
The home directory of the person running fvwm.
The X11 version.
The X11 revision number.
The X server vendor.
The X server release number.
The screen number.
The screen width in pixels.
The screen height in pixels.
Some distance/pixel measurement for the horizontal direction, I think.
Some distance/pixel measurement for the vertical direction, I think.
Number of color planes for the X server display
Number of bits in each rgb triplet.
The X11 default visual class, e.g. PseudoColor.
Yes or No, Yes if the default visual class is neither StaticGrey or GreyScale.
The visual class that fvwm is using, e.g. TrueColor.
Yes or No, Yes if the FVWM_CLASS is neither StaticGrey or GreyScale.
The fvwm version number, ie 2.0
Some combination of SHAPE, XPM, NO_SAVEUNDERS, and M4, as defined in configure.h at compile time.
The directory where fvwm looks for .fvwm2rc and modules by default, as determined at compile time.
The value of $FVWM_USERDIR.
The value of $SESSION_MANAGER. Undefined if this variable is not set.
define(TWM_TYPE,``fvwm'')dnl define(SERVERHOST,``spx20'')dnl define(CLIENTHOST,``grumpy'')dnl define(HOSTNAME,``grumpy'')dnl define(OSTYPE,``SunOS'')dnl define(USER,``nation'')dnl define(HOME,``/local/homes/dsp/nation'')dnl define(VERSION,``11'')dnl define(REVISION,``0'')dnl define(VENDOR,``HDS human designed systems, inc. (2.1.2-D)'')dnl define(RELEASE,``4'')dnl define(SCREEN,``0'')dnl define(WIDTH,``1280'')dnl define(HEIGHT,``1024'')dnl define(X_RESOLUTION,``3938'')dnl define(Y_RESOLUTION,``3938'')dnl define(PLANES,``8'')dnl define(BITS_PER_RGB,``8'')dnl define(CLASS,``PseudoColor'')dnl define(COLOR,``Yes'')dnl define(FVWM_VERSION,``1.24l'')dnl define(OPTIONS,``SHAPE XPM M4 '')dnl define(FVWM_MODULEDIR,``/local/homes/dsp/nation/modules'')dnl define(FVWM_USERDIR,``/local/homes/dsp/nation/.fvwm'')dnl define(SESSION_MANAGER,``local/grumpy:/tmp/.ICE-unix/440,tcp/spx20:1025'')dnl
FvwmM4 is the result of a random bit mutation on a hard disk, presumably a result of a cosmic-ray or some such thing.