Dominik Vogt <dominik.v...@gmx.de> writes: > On Mon, Sep 15, 2014 at 02:08:44PM -0400, Dan Espen wrote: >> Not sure I want to work in the mvwm tree. >> Not fond of the name, > > Neither me, but more because the "M" gets in the way with tab > completion in the subsirs (also matches Makefile*).
I want to avoid the impression of a fork, and F=Feline is fine with me. But our poor Angel died and I'm too old for another cat. >> and don't want to see FvwmCPP go away. > > But the module is already back. :-) > > I think at the moment it should also be possible to add the fvwm > modules to the module path and use them with the new core. If not, > I'm interested in finding out what has to be done to make them > compatible. Fvwm probably has some compatibility check that might > prevent it. Not sure what you mean with the last paragraph. The built in module path should deal with running multiple versions of modules. I usually install fvwm to something like: ~/fvwm/2.6.6/ <-- version number, but could be anything. -- Dan Espen
