1= fvwm-convert-2.6(1) 2 3== NAME 4 5fvwm-convert-2.6 - convert fvwm 2.4.x configuration file to fvwm 2.6 style 6 7== SYNOPSIS 8 9*fvwm-convert-2.6* [__--follow-read__|_-f_] [__--help__|_-h_] source 10[_dest_] 11 12== OPTIONS 13 14The following options are supported: 15 16--help | -h:: 17 Prints a usage message to the screen. 18--follow-read | -f:: 19 Follows files found along with the *Read* command. 20 21== DESCRIPTION 22 23*fvwm-convert-2.6* converts an fvwm 2.4.x configuration file into a fvwm 242.6 file with compatible syntax. It is not suitable to convert older 2.x 25configuration files. Please use *fvwm-convert-2.2* to convert these to 26the 2.2.x format first, and then if necessary *fvwm-convert-2.4* 27 28By default, *fvwm-convert-2.6* won't look for a given config file. This 29must be specified as the first parameter to *fvwm-convert-2.6.* 30Different source and destination files may be given. If the destination 31file already exists, this program exits. If no destination file is 32given, then the filename is the same name as the source file with the 33suffix ".converted" added. Without an absolute path given as the 34destination path to the destination file, the program will create the 35destination file in the CWD. 36 37*fvwm-convert-2.6* makes the following changes: 38 39*Style lines*:: 40 In fvwm 2.4, most style options could be negated from their 41 counterparts using NoFoo -- fvwm-convert-2.6 corrects this by now 42 using !Foo. 43*ModulePath*:: 44 In fvwm 2.4 and beyond, the ModulePath is compiled into fvwm. 45 *fvwm-convert-2.6* comments out any ModulePath commands it finds. If 46 you are using your own modules, (not the ones that come with fvwm), 47 you will have to fix your configuration file after using 48 *fvwm-convert-2.6*. 49*Conditional command syntax*:: 50 In fvwm 2.4, the conditional command options were whitespace-separated 51 -- they should now be comma-separated instead. In addition, the older 52 syntax to Next and Prev of using [*] to denote all windows has been 53 removed entirely. Both these checks and conversions are done on 54 function commands, key/mouse bindings. 55*WindowShadeSteps*:: 56 In fvwm 2.4, the WindowShadeSteps command is replaced by the 57 WindowShadeSteps Style option. *fvwm-convert-2.6* makes this change. 58*FvwmTheme*:: 59 In fvwm 2.6, the FvwmTheme module is replaced by a series of Colorset 60 commands. Whilst *fvwm-convert-2.6* will try and make this change, it 61 is still recommended that this is checked after conversion. 62*EdgeResistance*:: 63 In fvwm 2.6, the EdgeResistance command is has been split to include 64 an additional style option for EdgeMoveResistance. *fvwm-convert-2.6* 65 makes any changes necessary. 66*StartFunction / RestartFunction / InitFunction*:: 67 In fvwm 2.6, the need for using InitFunction and/or RestartFunction is 68 redundant when StartFunction is read at both of these times. 69 *fvwm-convert-2.6* attempts to convert this. 70*Read*:: 71 If *-f* or *--follow-read* is given, any files *fvwm-convert-2.6* can 72 detect and open will be converted automatically, else a list of files 73 that can be followed are printed to the screen. 74 75== BUGS 76 77_InitFunction_ and _RestartFunction_ and hence _StartFunction_ are 78printed at the end of the files -- this slight reordering might put some 79comments before in an odd spot. 80 81When converting over FvwmTheme lines, the colorset definitions might 82well be broken, but these cannot easily be converted. 83 84Bug reports can be sent to the fvwm-workers mailing list (see the 85_FAQ_). 86 87== AUTHOR 88 89Thomas Adam <thomas@fvwm.org> 90