9.12. Functions.fvwmconf

Another important part of the configuration. Almost all FVWM functions are defined here, except 5-6 of core functions in Main.fvwmconf which are reading the rest of the configuration. They are sorted in logical groups and are used widely in almost every part of the configuration, and particularly from the FvwmScript scripts. Main groups of NsCDE FVWM functions are:

For a FVWM function description see fvwm(1), in this file there is a plethora of examples, and for user usage is the most interesting part placeholders for functions which are here merely for programs to not complain about missing them and which should be overridden in user's local extension $FVWM_USERDIR/Functions.fvwmlocal - this extension file will be read by the main configuration immediately after processing Functions.fvwmconf. This functions are:

Another useful function is conditional execution function f_WarpOrExec. It takes 3+ arguments. First is the window name or class (or icon, resource) name, second is the binary to check in $PATH>, and 3rd to the rest of the command line is what to execute with all arguments included. If window with name from arg1 is already present on $DISPLAY, it will not be executed, but pointer will be simply pointed to that window. If window was iconified, or function called from another workspace or page, window will be deiconified, and workspace and/or current page changed to one where existing window is residing.

It is pointless and bad idea for this file to be overridden by the local copy of the conf (fvwmconf, not fvwmlocal) file, because a lot of things depends on this functions. Regular update of NsCDE software version will almost certain make setup with missing or incompatible functions.