FvwmCpp(1) General Commands Manual FvwmCpp(1)

FvwmCpp - the FVWM Cpp pre-processor

FvwmCpp is spawned by fvwm, so no command line invocation will work.

When called, this module will attempt to have /usr/lib/cpp pre-process the file specified in its invocation, and then have fvwm read the resulting file.

FvwmCpp can be invoked by inserting the line 'FvwmCpp' in the .fvwmrc file. It can also be called from a menu or mouse binding. If the user wants his entire .fvwmrc file pre-processed with FvwmCpp, then fvwm should be invoked as:

fvwm2 -cmd "FvwmCpp .fvwmrc"

Some options can be specified on the command line:

Lets you pass an option to the cpp program. Not really needed as any unknown options will be passed on automatically.

Instead of invoking "/usr/lib/cpp", fvwm will invoke name.

Instead of creating a random unique name for the temporary file for the preprocessed rc file, this option will let you specify the name of the temporary file it will create.

Causes the temporary file create by Cpp to be retained. This file is usually called "/tmp/fvwmrcXXXXXXXXXX"

FvwmCpp 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 X11 version.
The X11 revision number.
The X server vendor.
The X server release 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 visual class, ie PsuedoColor.
Yes or No, Yes if the display class is neither StaticGrey or GreyScale.
The fvwm version number, ie 2.0
Some combination of SHAPE, XPM, NO_SAVEUNDERS, and Cpp, as defined in configure.h at compile time.
The directory where fvwm looks for .fvwmrc and modules by default, as determined at compile time. 

#define TWM_TYPE fvwm
#define SERVERHOST spx20
#define CLIENTHOST grumpy
#define HOSTNAME grumpy
#define OSTYPE SunOS
#define USER nation
#define HOME /local/homes/dsp/nation
#define VERSION 11
#define REVISION 0
#define VENDOR HDS human designed systems, inc. (2.1.2-D)
#define RELEASE 4
#define WIDTH 1280
#define HEIGHT 1024
#define X_RESOLUTION 3938
#define Y_RESOLUTION 3938
#define PLANES 8
#define BITS_PER_RGB 8
#define CLASS PseudoColor
#define COLOR Yes
#define FVWM_VERSION 2.0 pl 1
#define OPTIONS SHAPE XPM Cpp
#define FVWM_MODULEDIR /local/homes/dsp/nation/modules

Module configurations do not become active until fvwm2 has restarted if you use FvwmCpp on startup. FvwmCpp creates a temporary file and passes this to fvwm2, so you would have to edit this file too. There are some problems with comments in your .fvwmrc file. The comment sign # is misinterpreted by the preprocessor. This has usually no impact on functionality but generates annoying warning messages. The sequence /* is interpreted as the start of a C comment what is probably not what you want in a filename. You might want to try /?* (for filenames only) or /\* or "/*" instead. Macros are not replaced within single (') or double quotes ("). Use backquotes (`) to circumvent this. Fvwm2 accepts backquotes for quoting and at least FvwmButtons does too. The preprocessor may place a space after a macro substitution, so with

#define MYCOMMAND ls
"Exec "MYCOMMAND" -l"

you might get

"Exec "ls " -l" (two words)

and not

"Exec "ls" -l" (one word).

FvwmCpp is the result of a random bit mutation on a hard disk, presumably a result of a cosmic-ray or some such thing.

12/12/94 3rd Berkeley Distribution