> 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".
Hrm, this sounds like rather strange behavior. What I do is create
~/.fvwm (a subdir)
~/.fvwm/fvwmrc
~/.fvwm/fvwm-styles
~/.fvwm/fvwm-menus
~/.fvwm/fvwm-modules
... etc ...
in fvwm-menus I have the following menu:
AddToMenu ReReadIt "*fvwm.xpm*" Title
+ "&Key bindings" Read /home/todd/.fvwm/fvwm-keys
+ "&Mouse bindings" Read /home/todd/.fvwm/fvwm-mouse
+ "M&odules" Read /home/todd/.fvwm/fvwm-modules
+ "&Paths" Read /home/todd/.fvwm/fvwm-paths
+ "&Styles" Read /home/todd/.fvwm/fvwm-style
Which you could easily adapt to be:
AddToFunc RestartFvwmButtons
+ "I" KillModule FvwmButtons
+ "I" Read /wherever/your/rcfile/for/goodstuffis
+ "I" Module FvwmButtons
I separated the files out, as I found that reading
them all isn't really necessary, and things like
re-reading all of the menus w/out putting
'DestroyMenu' infront of each menuname created
interestingly doubled-menus and functions that
would do things twice...
--
Todd Fries...tfries_at_umr.edu
http://www.cs.umr.edu/~tfries
--
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 Thu Dec 07 1995 - 03:04:13 GMT