>Do you mean you run X without a window manager and then run fvwm in xterm >and don't see any error message? I would think you should see the message >"no config file found, tried [5 locations mentioned in man page listed]". >If you actually don't see this error message, then you have some fvwm2rc.
Right. I exit fvwm, then restart it in an xterm. It really does read my rc file because some of the stuff happens (just not all of it). If it wasn't clear, I should also point out that in all these X sessions, I'm running on the exact same host machines as the exact same user with the exact same home directory and rc files and wot-not, my display is simply appearing on an assortment of different Windows and linux boxes courtesy of the NX software, and on all but one of these boxes everything works fine, fvwm simply picks on this one box to act like it ignores about half of my rc file (and the remote system it fails on is a Windows XP box running the exact same release of XP and the exact same nxclient as two other boxes it works fine on :-). I don't even know how it can tell which box I'm coming in from (though I guess the root window geometry is unique to this box). Since all the other X apps respond to button clicks fine, I'm calling this an fvwm bug for now, but it is always hard to guess who might be responsible when there are so many pieces involved.
