The modifier value can be one of the following: A (any), C (control), S (shift), M (meta), N (none), or 1-5, representing the X Modifiers - run xmodmap to see which X modifier is which. Any combination of these letters is also acceptable. The following contexts are valid: R (root window), W (application window), D (desktop manager window - PCManFM desktop manager for instance), T (title bar), S (window side, top, bottom), - _ (left side, right side, top, bottom respectively), F (window frame corners), ^ v (left, right, top, bottom corners respectively), I (icon window), 0-9 (titlebar buttons) and A (all contexts). The context value defines where the binding will be applied. Note that the (window) argument is optional.

For instance, the following example will launch an XTerm on an Alt+F2 keypress: Key F2 A 1 Exec xterm. The syntax of the command takes the following form: Key/Mouse (window) button/key name context modifiers action. Keyboard or bindings can be defined in the configuration file with the Key or Mouse command. Desks can be navigated using the pager module (if it is configured to show a number of desks) or with the GoToDesk command - GoToDesk +1 will move to the next desk, relative to the currently used desk. The number of desks available in FVWM is very large, the minimum desk number is -2147483648 and the maximum is 2147483647. For instance, the command GoToPage -1p +0p will move the viewport 1 page to the left of the current page. Pages can be navigated using the pager module or with the GoToPage command which could be mapped to a keyboard shortcut or menu entry. For instance, adding DesktopSize 3x3 to your configuration file will give you 9 pages, arranged in a 3x3 grid. The number of pages used can be defined with the DesktopSize command. FVWM refers to workspaces as desks and viewports as pages. See for a description of the differences between workspaces and viewports. The virtual desktopįor its virtual desktop, FVWM implements both workspaces (used by window managers such as Metacity and Openbox) and viewports (used by window managers such as Compiz). Tip: You can split up your configuration into multiple files and then source those files from the main configuration file using the read command. The fvwm-themes project also provides ready-made configurations though it should be noted that these have not been updated since 2003 and may require modifications to work correctly with more recent FVWM versions. However, they can still be viewed on GitHub. As such, the older sample configuration files are no longer provided. The following configuration locations are supported as of version 2.6.8, but may not be supported in the future:Īs of version 2.6.7, FVWM ships with a new default configuration, located in /usr/share/fvwm/default-config. The following configuration file locations are supported: Using this method, nm-applet could be started in the following manner:

You can also use just StartFunction and prepend your commands with Test commands which check whether the window manager has started or restarted and run the action only if the test is true. For example, if one wanted to start network-manager-applet on startup (but not for any subsequent restarts of the window manager) one could add the nm-applet command to the InitFunction: You can add your own actions to any of these functions using the AddToFunc command. ExitFunction - executed when exiting FVWM.RestartFunction - executed only when FVWM is restarted.InitFunction - executed only when FVWM is first initialised.StartFunction - executed when FVWM is first initialised and on restarts.Note: It is recommended that you only use the StartFunction and make use of the Test command - explained below.įVWM provides a number of functions to start modules or applications when initialising, restarting or exiting the window manager.

Iconbox icon left