Lots of Read and environmental variables

Happy to see the forums back online, thank you, Thomas!

And here comes a basic question about configuration file writing principle:

Is it okay to make a configuration file consisting of

Read /this/file
Read /that/file

only?

The idea is to make a dozen or two configuration files for each aspect of wm’s behavior - keybindings, window decorations and so on. That would make configuration file more readable, and one could make a configuration submenu where each item would point to coresponding file.

Is it okay to set like a dozen of envionmental variables for ‘default’ applicaations like browser, file manager etc.?

Yes, that’s fine. See: fvwmwiki.xteddy.org/fvwmwiki/Con … structure/

See: viewtopic.php?f=40&t=1505

– Thomas Adam

I feel more comfortable with the multi-file approach as I can easily activate and deactivate parts of fvwm configuration. Although this can be be done in your favourite editor, being a computer illiterate makes larger files more difficult to handle. For example, this is my config file:

[code]Read $./conf/xinerama.fvwm
Read $./conf/startfunction.fvwm
Read $./conf/functions.fvwm
#Read $./conf/backer.fvwm
Read $./conf/colors.fvwm
Read $./conf/style.fvwm
#Read $./conf/decor.fvwm
Read $./conf/keys.fvwm
Read $./conf/mouse.fvwm
Read $./conf/cursor_theme.fvwm
Read $./conf/VirtualDesktops.fvwm
Read $./conf/menus.fvwm
Read $./conf/pager.fvwm
Read $./conf/buttons.fvwm

Read $./conf/TaskBar.fvwm

Read $./conf/IconMan.fvwm
Read $./conf/IconBox.fvwm
Read $./conf/kuake_terminal.fvwm
Read $./conf/kuake_terminal_1.fvwm
#Read $./conf/exitpanel.fvwm[/code]

Do you mean to activate some fvwm configuration using the menu while fvwm is running? I normally use functions for this, and I would be interested to know if you try to implement it.

Cheers!