> Note that setting ModulePath is potentially still a bad thing to do, > when the Module command already takes an absolute file name as means > of opening a module.
Hmm. I probably will use the full path then, thanks. > [1] This point about "+" used after your additions is a nice idea, > but ultimately incorrect for any proper use of ordering. You > shouldn't be writing modules of the same name as the ones FVWM ship, > only to then rely on the search order of what's in the ModulePath. > That way leads to fail, and anyone doing that now will get bitten on > the arse if it ever changes. So don't do it. Who would do that, I wonder.
