Jean-Marc Lasgouttes wrote...
> There could be two files that fvwm searches for:
>
> - global.fvwmrc, which is always read if it exists
> - default.fvwmrc, which is read if the user does not have a .fvwmrc
>
> The sysadmin could choose which files he provides for the users.
Or even easier: using a new directive
ConfigPath: $HOME:/usr/lib/X11/fvwm2
, a "combined" system.fvwm2rc could consist of
.... a lot of defaults .... and as the last line:
Read ".fvwm2rc" # either ~/.fvwm2rc or /usr/lib/X11/fvwm2/.fvwm2rc
which would include either the user's config files or the system
equivalents.
Or, using the Pipe mechanism I saw on this list earlier on (and which I
think would be _very_ useful to include as a standard feature), one
could easily write
Read "| [ -f $HOME/.fvwm2rc ] && cat $HOME/.fvwm2rc || cat /usr/lib/X11/fvwm2/system.fvwm2rc"
Or a combination of both methods could be chosen.
Just a thought.
Martin
--
| S I E M E N S | Martin.Kraemer_at_mch.sni.de | Siemens Nixdorf
| ------------- | Voice: +49-89-636-46021 | Informationssysteme AG
| N I X D O R F | FAX: +49-89-636-44994 | 81730 Munich, Germany
~~~~~~~~~~~~~~~~My opinions only, of course; pgp key available on request
--
Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
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 May 29 1996 - 08:45:43 BST