I'm going through the ENUCFE (Endless New User Configuration File
Editing) phase with Fvwm 2.0.39. To facilitate playing with modules,
I added functions like this to my .fvwmrc file:
AddToFunc RestartFvwmButtons
+ "I" KillModule FvwmButtons
+ "I" Module FvwmButtons
...which I call from a menu. The intention was to be able to play
with config lines for a module and restart just the module, instead of
restarting Fvwm.
It doesn't work. Even though the above function kills off the current
FvwmButtons process and replaces it with a new one, the new one uses
the old process's configuration. Restarting fvwm itself *does* make
the new configuration lines "take".
The FvwmButtons man page says
"During initialization, FvwmButtons will search for a
configuration file.... The configuration file will be the one
which fvwm used during its initialization."
Actually, no file is involved at all. It might be better to say
"During initialization, FvwmButtons asks fvwm for a configuration.
Fvwm responds with the contents of the configuration file that was
read by fvwm when fvwm was started."
This applies to the other modules too.
--
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Wed Dec 06 1995 - 15:40:27 GMT