Re: fvwm and post.hook problem
- To: debian-user@lists.debian.org
- Subject: Re: fvwm and post.hook problem
- From: Stefan Bellon <sbellon@sbellon.de>
- Date: Fri, 09 Apr 2004 18:30:58 +0200
- Message-id: <[🔎] 4c9d0291dcsbellon@sbellon.de>
- References: <1IZyT-4fQ-17@gated-at.bofh.it> <1IZyT-4fQ-19@gated-at.bofh.it> <1IZyT-4fQ-21@gated-at.bofh.it> <1IZyT-4fQ-23@gated-at.bofh.it> <1IZyT-4fQ-15@gated-at.bofh.it> <1J3VK-8c3-11@gated-at.bofh.it>
Cameron Hutchison wrote:
> Once upon a time Stefan Bellon said...
[snip]
> > 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.
Essentially I have done the same. I know created one single .fvwm2rc
file which contained all the stuff from /etc/X11/fvwm and my post.hook
file. Only one hook is present now, the menudefs.hook as the other have
been discarded.
[snip]
> 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.
I completely agree. I couldn't have worded it better!
--
Stefan Bellon
Reply to: