Update for fvwm3 1.1.4 release

Author: ThomasAdam

Man/FvwmEvent.html

@@ -325,9 +325,44 @@ <h2 id="_configuration_options">CONFIGURATION OPTIONS</h2>
 </div>
 <div class="paragraph">
 <p>The monitor_* events do not operate in a window context (as there isn&#8217;t
-one), but react to when a monitor is plugged in (enabled), unplugged
-(disabled), focused (focus) or changed (resized/rotated, etc., which
-will only be true if the monitor is already active).</p>
+one).</p>
+</div>
+<div class="paragraph">
+<p>The given event command is also passed the following values:</p>
+</div>
+<div class="literalblock highlight">
+<div class="content">
+<pre>$0: monitor_event_name (for example: monitor_changed)
+$1: monitor_name (the RandR name of the monitor)</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>For example, consider the following:</p>
+</div>
+<div class="literalblock highlight">
+<div class="content">
+<pre>    DestroyFunc RandRFunc
+    AddToFunc   RandRFunc
+    + I Exec exec xmessage "Monitor $1 had this event: $0"
+
+    DestroyModuleConfig FE-Monitor: *
+    *FE-Monitor: monitor_changed RandRFunc
+    *FE-Monitor: monitor_enabled RandRFunc
+
+    KillModule FvwmEvent FE-Monitor
+    Module FvwmEvent FE-Monitor</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>When, say, the monitor_changed event is triggered, RandRFunc is run, with the
+monitor name passed in as the first argument, and the monitor event as the
+second argument.  In this way it is possible to do further matching if
+required.</p>
+</div>
+<div class="paragraph">
+<p><strong>NOTE</strong>: Using <code>PassID</code> with a configuration which includes monitor_ lines
+won&#8217;t work since there is no ID to pass back.  If <code>PassID</code> is still required,
+separate out monitor events into their own FvwmEvent configuration.</p>
 </div>
 <div class="paragraph">
 <p>The echo event is generated whenever Fvwm receives an Echo command.</p>

Man/FvwmIconMan.html

@@ -505,8 +505,8 @@ <h2 id="_configuration_options">CONFIGURATION OPTIONS</h2>
 <dd>
 <p>A printf like format string which describes the string to be printed
 in the manager window for each managed window. Possible flags are: %t,
-%i, %c, and %r for the window&#8217;s title, icon title, class, or resource
-name, respectively. The default is "%c: %i".</p>
+%i, %c, %r, and %s for the window&#8217;s title, icon title, class, resource
+name, or screen respectively. The default is "%c: %i".</p>
 </dd>
 <dt class="hdlist1">*FvwmIconMan: [id] IconName iconstring</dt>
 <dd>
@@ -692,7 +692,7 @@ <h2 id="_configuration_options">CONFIGURATION OPTIONS</h2>
 <dd>
 <p>Assigns the specified <em>weight</em> to windows that match <em>pattern-list</em>.
 The list is made up of patterns of the form <em>type=pattern</em>, where type
-is one of <em>class</em>, <em>resource</em>, <em>title</em>, or <em>icon</em>, and pattern is an
+is one of <em>class</em>, <em>resource</em>, <em>title</em>, <em>icon</em>, or, <em>screen</em> and pattern is an
 expression of the same format used in the fvwm style command
 (minimalistic shell pattern matching). Multiple sort weights can be
 given. Each window is matched against the list of sort weights, in

Man/FvwmPager.html

@@ -412,14 +412,15 @@ <h3 id="_balloon_windows">BALLOON WINDOWS</h3>
 </div>
 <div class="dlist">
 <dl>
-<dt class="hdlist1">*FvwmPager: Balloons [type]</dt>
+<dt class="hdlist1">*FvwmPager: Balloons type</dt>
 <dd>
 <p>Show a balloon describing the window when the pointer is moved into a
 window in the pager. The default format (the window&#8217;s icon name) can
 be changed using <em>BalloonStringFormat</em>. If <em>type</em> is "Pager" balloons
-are just shown for an un-iconified pager; if <em>type</em> is "Icon" balloons
-are just shown for an iconified pager. If <em>type</em> is anything else (or
-null) balloons are always shown.</p>
+are just shown for an un-iconified pager. If <em>type</em> is "Icon" balloons
+are just shown for an iconified pager. If <em>type</em> is "All" (or any unused
+non blank value) balloons are always shown. If <em>type</em> is "None" balloons
+are never shown (the default behavior).</p>
 </dd>
 <dt class="hdlist1">*FvwmPager: BalloonFont font-name</dt>
 <dd>

Man/FvwmRearrange.html

@@ -324,6 +324,15 @@ <h3 id="_general_options">GENERAL OPTIONS</h3>
 such as <em>EwmhBaseStruts</em>; by default, FvwmRearrange will honour the
 working area. This option may place windows outside of the current monitor.</p>
 </dd>
+<dt class="hdlist1">-win_cmd <em>COMMAND</em></dt>
+<dd>
+<p>Runs the fvwm <em>COMMAND</em> in the context of every window that is rearranged.
+This can be used to set the state of all affected windows with the <em>COMMAND</em>
+"State n" so they can be matched using the "State n" conditional. The
+<em>COMMAND</em> is sent after the window is moved/resized, so any change in
+window&#8217;s size, adding removing title bars, etc, will not be used in
+computing the new position/size of the window.</p>
+</dd>
 </dl>
 </div>
 </div>
@@ -413,6 +422,12 @@ <h3 id="_filtering_options">FILTERING OPTIONS</h3>
 <p>Causes all windows on the desk to be cascaded/tiled instead of only
 windows that intersect the bounding box.</p>
 </dd>
+<dt class="hdlist1">-on_screen</dt>
+<dd>
+<p>Causes all windows on the monitor to be cascaded/tiled instead of only
+windows that intersect the bounding box. Has no effect when used together
+with <em>-desk</em>.</p>
+</dd>
 </dl>
 </div>
 </div>

Man/fvwm3.html

@@ -564,17 +564,7 @@ <h2 id="_randr_multi_screen_support">RANDR MULTI-SCREEN SUPPORT</h2>
 changes size, or has been added or removed.</p>
 </div>
 <div class="paragraph">
-<p>In addition to specific <strong>FvwmEvent</strong> conditions which can be used to track a
-monitor&#8217;s change, there is a function called <em>RandRFunc</em> which the user can
-define to be run when a screen event occurs (such as
-enabling/disabling/resolution change):</p>
-</div>
-<div class="literalblock highlight">
-<div class="content">
-<pre>DestroyFunc RandRFunc
-AddToFunc   RandRFunc
-+ I Exec exec xmessage "A screen changed"</pre>
-</div>
+<p>These are controlled by <strong>FvwmEvent</strong>.</p>
 </div>
 </div>
 </div>
@@ -2085,12 +2075,13 @@ <h2 id="_command_expansion">COMMAND EXPANSION</h2>
 <p>Please refer to the <strong>Colorsets</strong> section for details about colorsets.</p>
 </div>
 </dd>
-<dt class="hdlist1">$[math.+.&lt;x&gt;,&lt;y&gt;] $[math.-.&lt;x&gt;,&lt;y&gt;] $[math.*.&lt;x&gt;,&lt;y&gt;] $[math./.&lt;x&gt;,&lt;y&gt;] $[math.%.&lt;x&gt;,&lt;y&gt;] $[math.^.&lt;x&gt;,&lt;y&gt;]</dt>
+<dt class="hdlist1">$[math.+.&lt;x&gt;,&lt;y&gt;] $[math.-.&lt;x&gt;,&lt;y&gt;] $[math.*.&lt;x&gt;,&lt;y&gt;] $[math./.&lt;x&gt;,&lt;y&gt;] $[math.%.&lt;x&gt;,&lt;y&gt;] $[math.^.&lt;x&gt;,&lt;y&gt;] $[math.&lt;.&lt;x&gt;,&lt;y&gt;] $[math.&gt;.&lt;x&gt;,&lt;y&gt;]</dt>
 <dd>
 <p>The math expansion variables can be used to do some basic arithmetic
 on the integers &lt;x&gt; and &lt;y&gt;. These expressions can be used to add
 (&#43;), subtract (-), multiply (*), divide (/), modulus
-(%), and exponentiation (^). This can be useful when computing
+(%), and exponentiation (^). Maximum (&gt;) returns the greater of
+two values, and minimum (&lt;) the lesser. This can be useful when computing
 the size of panels or locations of windows relative to a monitor, for
 example $[math.-.$[monitor.$[monitor.primary].height],200] will
 subtract 200 pixels from the height of the primary monitor. These can

Man/fvwm3all.html

@@ -602,17 +602,7 @@ <h2 id="_randr_multi_screen_support">RANDR MULTI-SCREEN SUPPORT</h2>
 changes size, or has been added or removed.</p>
 </div>
 <div class="paragraph">
-<p>In addition to specific <strong>FvwmEvent</strong> conditions which can be used to track a
-monitor&#8217;s change, there is a function called <em>RandRFunc</em> which the user can
-define to be run when a screen event occurs (such as
-enabling/disabling/resolution change):</p>
-</div>
-<div class="literalblock highlight">
-<div class="content">
-<pre>DestroyFunc RandRFunc
-AddToFunc   RandRFunc
-+ I Exec exec xmessage "A screen changed"</pre>
-</div>
+<p>These are controlled by <strong>FvwmEvent</strong>.</p>
 </div>
 </div>
 </div>
@@ -2123,12 +2113,13 @@ <h2 id="_command_expansion">COMMAND EXPANSION</h2>
 <p>Please refer to the <strong>Colorsets</strong> section for details about colorsets.</p>
 </div>
 </dd>
-<dt class="hdlist1">$[math.+.&lt;x&gt;,&lt;y&gt;] $[math.-.&lt;x&gt;,&lt;y&gt;] $[math.*.&lt;x&gt;,&lt;y&gt;] $[math./.&lt;x&gt;,&lt;y&gt;] $[math.%.&lt;x&gt;,&lt;y&gt;] $[math.^.&lt;x&gt;,&lt;y&gt;]</dt>
+<dt class="hdlist1">$[math.+.&lt;x&gt;,&lt;y&gt;] $[math.-.&lt;x&gt;,&lt;y&gt;] $[math.*.&lt;x&gt;,&lt;y&gt;] $[math./.&lt;x&gt;,&lt;y&gt;] $[math.%.&lt;x&gt;,&lt;y&gt;] $[math.^.&lt;x&gt;,&lt;y&gt;] $[math.&lt;.&lt;x&gt;,&lt;y&gt;] $[math.&gt;.&lt;x&gt;,&lt;y&gt;]</dt>
 <dd>
 <p>The math expansion variables can be used to do some basic arithmetic
 on the integers &lt;x&gt; and &lt;y&gt;. These expressions can be used to add
 (&#43;), subtract (-), multiply (*), divide (/), modulus
-(%), and exponentiation (^). This can be useful when computing
+(%), and exponentiation (^). Maximum (&gt;) returns the greater of
+two values, and minimum (&lt;) the lesser. This can be useful when computing
 the size of panels or locations of windows relative to a monitor, for
 example $[math.-.$[monitor.$[monitor.primary].height],200] will
 subtract 200 pixels from the height of the primary monitor. These can

Man/fvwm3commands.html

@@ -701,9 +701,6 @@ <h3 id="_miscellaneous_commands">Miscellaneous Commands</h3>
 <p><em>nls</em> which prints information on the locale catalogs that fvwm used</p>
 </div>
 <div class="paragraph">
-<p><em>style</em> which prints information on fvwm styles. <em>verbose</em> can be 1.</p>
-</div>
-<div class="paragraph">
 <p><em>bindings</em> which prints information on all the bindings fvwm has: key
 and mouse bindings. <em>verbose</em> has no effect with this option.</p>
 </div>
@@ -1667,40 +1664,56 @@ <h3 id="_focus_mouse_movement">Focus &amp; Mouse Movement</h3>
 <p><em>CursorBarrier</em> only works if fvwm is complied with the XFixes extension.</p>
 </div>
 </dd>
-<dt class="hdlist1"><strong>CursorMove</strong> <em>horizontal</em>[p] <em>vertical</em>[p]</dt>
+<dt class="hdlist1"><strong>CursorMove</strong> [screen <em>RANDRNAME</em>] <em>horizontal</em>[p] <em>vertical</em>[p]</dt>
 <dd>
-<p>Moves the mouse pointer by <em>horizontal</em> pages in the X direction and
-<em>vertical</em> pages in the Y direction. Either or both entries may be
-negative. CursorMove can only move the mouse cursor to a relative
-position. To move the mouse cursor to an absolute position, see
-<strong>WarpToWindow</strong>. Both horizontal and vertical values are expressed in
-percent of pages, so</p>
+<p>Without the <em>screen</em> option, <em>CusorMove</em> moves the mouse cursor a
+<em>horizontal</em> distance and <em>vertical</em> distance from its current position.
+The values are expressed as either a percent of the virtual desktop size,
+or a pixel distance by appending a '<em>p</em>' to the value. Either or both
+entries may be negative. For example,</p>
 <div class="literalblock highlight">
 <div class="content">
-<pre>CursorMove 100 100</pre>
+<pre># Move down and right by one full page.
+CursorMove 100 100
+
+# Move down two full pages.
+CursorMove 0 200
+
+# Move half page right and quarter page up.
+CursorMove 50 -25
+
+# Move left 100 pixels and down 50 pixels.
+CursorMove -100p 50p</pre>
 </div>
 </div>
 <div class="paragraph">
-<p>means to move down and right by one full page.</p>
+<p>If the option <em>screen</em> followed by a valid RandR monitor name is included,
+<em>CursorMove</em> will move the cursor to the absolute position (starting at
+the top left corner) given by the arguments, as either percent values
+of the monitor&#8217;s size, or an absolute location with the '<em>p</em>' suffix.
+For example,</p>
 </div>
 <div class="literalblock highlight">
 <div class="content">
-<pre>CursorMove 50 25</pre>
+<pre># Move cursor to center of monitor DP-1
+CursorMove screen DP-1 50 50
+
+# Move cursor to the exact location (400, 200) of monitor DP-2
+CursorMove screen DP-2 400p 200p</pre>
 </div>
 </div>
 <div class="paragraph">
-<p>means to move right half a page and down a quarter of a page.
-Alternatively, the distance can be specified in pixels by appending a
-'<em>p</em>' to the horizontal and/or vertical specification. For example</p>
-</div>
-<div class="literalblock highlight">
-<div class="content">
-<pre>CursorMove -10p -10p</pre>
-</div>
+<p>When moving to a specified <em>screen</em>, the <em>horizontal</em> and <em>vertical</em>
+values are always shifted to be inside the current page of the specified
+monitor. For instance '50', '150', and '-150' will all be the center of the
+monitor, and will not change monitor&#8217;s page. Use <strong>GotoPage</strong> to change the
+page of a specified monitor. Negative values can be used to specify distance
+from the right/bottom corner of the monitor.</p>
 </div>
 <div class="paragraph">
-<p>means move ten pixels up and ten pixels left. The CursorMove function
-should not be called from pop-up menus.</p>
+<p><em>CusorMove</em> can only move the cursor relative to its current position,
+or to an absolute position on a given monitor. To move the cursor relative
+to a window, use <strong>WarpToWindow</strong>.</p>
 </div>
 </dd>
 <dt class="hdlist1"><strong>FlipFocus</strong> [NoWarp]</dt>

Man/fvwm3styles.html

@@ -26,6 +26,81 @@ <h2 id="_controlling_window_styles">Controlling Window Styles</h2>
 alphabetically. The description of the <strong>Style</strong> command can be found at
 the end of this section.</p>
 </div>
+<div class="paragraph">
+<p>The commands: <strong>FocusStyle</strong>, <strong>Style</strong>, and <strong>WindowStyle</strong> can accept optional
+conditional components to match some properties of a window.</p>
+</div>
+<div class="paragraph">
+<p>For example:</p>
+</div>
+<div class="literalblock highlight">
+<div class="content">
+<pre>Style (Name mc) Sticky</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>Will make a window whose name matched 'mc' <em>Sticky</em>.</p>
+</div>
+<div class="literalblock highlight">
+<div class="content">
+<pre>Style (Name mc, Class XTerm) StartIconic</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>This example will start an xterm(1) window whose WM_CLASS matches 'XTerm' and
+name is 'mc'.</p>
+</div>
+<div class="paragraph">
+<p>A valid list of properties to test against are:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Resource</p>
+</li>
+<li>
+<p>Class</p>
+</li>
+<li>
+<p>Name</p>
+</li>
+<li>
+<p>Icon</p>
+</li>
+<li>
+<p>WindowID</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>The matching of the properties specified for any <strong>Style</strong> line are ANDed
+together, and for styles to be applied, <strong>all</strong> properties must match.</p>
+</div>
+<div class="paragraph">
+<p><strong>NOTE</strong>: To destroy a style line with window properties, <strong>DestroyStyle</strong>
+should be used.  For example:</p>
+</div>
+<div class="literalblock highlight">
+<div class="content">
+<pre>DestroyStyle (Name mc, Class XTerm)</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>It is not required to specify the style arguments when destroying a style,
+only the property components are required.</p>
+</div>
+<div class="paragraph">
+<p>Existing <strong>Style</strong> lines in the form:</p>
+</div>
+<div class="literalblock highlight">
+<div class="content">
+<pre>Style Application* Sticky, StartIconic</pre>
+</div>
+</div>
+<div class="paragraph">
+<p>are still supported, and their behaviour remains unchanged.</p>
+</div>
+<hr>
 <div class="dlist">
 <dl>
 <dt class="hdlist1"><strong>FocusStyle</strong> <em>stylename</em> <em>options</em></dt>

Man/index.html

@@ -2,8 +2,7 @@
 title: Fvwm3 Manual Pages
 showtitle: 1
 ---
-
-The following are the manual pages for fvwm3 version <strong>1.1.2</strong>.
+The following are the manual pages for fvwm3 version <strong>1.1.4-1-gc7a86a9c</strong>.
 <div id="markdown-toc">
 <ul class="sectlevel1">
 <li><a href="#_fvwm3">Fvwm3</a></li>

_config.yml

@@ -15,7 +15,7 @@ url: "https://www.fvwm.org" # the base hostname & protocol for your site
 
 # FVWM release version
 fvwm2-version: 2.7.0
-fvwm3-version: 1.1.2
+fvwm3-version: 1.1.4
 
 # Highlight fvwm2rc code
 fvwm2rc: False