Re: FVWM: restarting modules

From: Charles Hines <>
Date: Fri, 8 Dec 1995 08:56:50 -0500

>>>>> "Peter" == Peter Funk <pf_at_artcom0.north.de> writes:

Peter> If this is so, this behaviour must have been changed anywhere
Peter> between version 1.24r to 2.0.x, where the 'GoodStuff'-Module
Peter> (ancestor of FvwmButtons) accesses the .fvwmrc file directly,
Peter> so that a shutdown and restart of 'GoodStuff' allone will
Peter> reflect new button definitions in .fvwmrc.

Peter> I don't have 2.0.x yet, so it would be kind, if someone could
Peter> verify Petes observations.

That is the case. Fvwm reads the config files, and the modules get
their config info from fvwm. The reason being that this is the only
way for modules to deal w/ m4 and cpp preprocessing cleanly.

Granted, if you don't use these (which I don't) then the advantage of
just being able to restart a module and pick up it's new config is
lost.

On the TO-DO list I have plans to update the FvwmTalk module to be
able to accept module config info, which will help here (you can make
small changes on the fly quickly that way).

Or you can put the module config info in a separate file and use the
'Read <file>' command to load the changes without restarting fvwm.

Chuck
--
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 Fri Dec 08 1995 - 07:57:08 GMT

This archive was generated by hypermail 2.3.0 : Mon Aug 29 2016 - 19:37:57 BST