<h1>The Fvwm2 Module</h1>

<h2>Changes Since the Fvwm1 Module</h2>
The Fvwm2 module differs from the Fvwm1 module in the same way as the two
programs differ. This means for example that a lot of the global options from
Fvwm1 has been moved into the "Styles of Windows" page, and is configurable on
a per-window basis.

<h2>Notes about the state of Fvwm2</h2>
Please remember that Fvwm2 is in beta state, which means that this module may
change at times. New pages may appear, and old ones may disappear as the
syntax and/or semantics of the Fvwm2 dotfile changes.

<h2>InitFunction and RestartFunction</h2>
If you want Fvwm2 to do special things at startup (e.g. start programs and
modules) you have to create the special functions <i>InitFunction</i> and
<i>RestartFunction</i>.

<i>InitFunction</i> is called when Fvwm2 is started (typically when you log in),
and <i>RestartFunction</i> is called whenever Fvwm2 is restarted. This means that
if you want to start som programs this is only necessary to do in
<i>InitFunction</i>, but if you start modules they must be started in
<i>RestartFunction</i> too since modules are killed when Fvwm2 restarts.

<h2><a name="howToUse">Typical Use of the Dotfile Generated Setup</a></h2>
Although I have tried to make the Fvwm2 module as complete as possible there
may be some things you cannot configure through the graphical interface
(typically fvwm modules not supported in the dotfile module). Therefore you
will typically "not" generate to the ~/.fvwm2rc file, but to the proposed
~/dot.fvwm2rc. This can be read in your ~/.fvwm2rc file using the <i>Read</i>
command:<p>

	--- start of ~/.fvwm2rc ---<br>
	Read dot.fvwm2rc<br>
	<br>
	* additional configuration lines *<br>
	--- end of ~/.fvwm2rc ---<br>