Once upon a time Stefan Bellon said...
> 
> Oh, the new version of FVWM has an impressive configuration "wizard".
> It's really not bad. But you cannot configure everything. And the
> configuration files it produces are split over a dozen files in
> ~/.fvwm/. So, if I want to add my more special changes, I wouldn't know
> where to put it.

/usr/share/doc/fvwm/NEWS.Debian.gz gave me enough clues of what has
happened with fvwm 2.5 in Debian. It seems the system of a common
system.fvwm2rc file with hooks has now been pushed aside for this new
"impressive configuration "wizard"". It is alluded to in the NEWS file,
but I cant find anything about it.

> I copied the old contents of /etx/X11/fvmw/* to my ~/.fvwm so that I
> maintain the state that I had until two days ago. But somehow this is
> still unsatisfying.

I went into /etc/X11/fvwm and copied all the .dpkg-old files back to
their original names, and copied DebianMenu to menudefs.hook.

Unfortunately the new DebianMenu file does not read main-menu-pre.hook,
so it is not possible to put your own stuff at the start of the menu, so
my customised menu has my stuff after the standard debian stuff now.
This I had to do in menudefs.hook where I used to do it in
main-menu-pre.hook.

Once I sorted this out, I was back to my old fvwm configuration.

Overall, I'd have to say I'm very disappointed with the approach taken
with fvwm 2.5 with regard to keeping existing configurations working.
There was quite an elaborate system for being able to hook personal
configuration into the system wide configuration, which encouraged you
to use these hooks rather than use your own complete fvwmrc. To now turn
around and break all that with a small notice in the NEWS file, saying
it has been done because of some new fancy configuration utility - to
encourage people to use this new utility - is quite disrespectful to the
users who have followed the system for configuring fvwm. A more orderly
transition should have been planned.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to