Mikhael Goikhman wrote: > > On 23 Apr 2002 09:57:50 +0200, szonyi calin wrote: > > > > Well, the features i did't like when switching from fvwm 2.2 to fvwm 2.4 > > were errors and warnings about my config (obsolete commands etc. ) > > > > So i had to change my old fvwm 2.2 config file to make fvwm 2.4 happy. > > :-( > > > > Is this a feature ?
Mikhael forgot to mention that the fvwm team take great pains to make this transition as easy and painless as possible by providing a conversion script called fvwm24_convert on older versions, but current cvs has recently renamed to fvwm-convert-2.4. It even has it's own man page! :) See Section 3.10 at http://www.fvwm.org/generated/FAQ.html > > Error messages inform you that a syntax was changed, this is a good thing. > You should correct all these errors only once when upgrading from one > major version to another. Ask yourself, why do you upgrade? Probably to > get new features, so you should learn a new syntax anyway. > > There are a lot of commands and options in FVWM, some are old, some new. > Sometimes the new contradict the old ones. It make sence to clean up the > mess from time to time to have a clean code and a clean syntax. Users > benefit from the clean code, because it has less hidden bugs, and from > the clean syntax, because it makes configuring easier and more intuitive. > > > Will it hapen again when fvwm 2.6 wil be released ? The current cvs version of file fvwm-convert-2.6 merely contains... #!/usr/bin/perl # -*-perl-*- # Convert .fvwm2rc from 2.4.x format to 2.6.x format. ... so I'm guessing if/when it becomes necessary, this file may grow. > > Maybe. But you should not be afraid of this. Think like this: they cared > to change this thing, means they worked on it and probably improved it. > At least this is how I try to think myself about evolutional changes in > programs that I use. > > Regards, > Mikhael. > -- :) Alex -- Visit the official FVWM web page at <URL: http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
