On Wed, 29 May 1996, Emilio Lopes wrote:
> liw> I think it may be a mistake to force a global config file to be
> liw> read. Or at least it will mean that the system admin can't put
> liw> too much of an environment there. For instance, he can't start
> liw> modules there, because not everyone will want them. A user
> liw> should be able to completely avoid a system.fvwmrc, IMHO.
> I think the same scheme can be done with fvwm2: the ~/.fvwm2rc can
> "Read" some system-wide file and the user can them do some
> "overloading" after the "Read". This works only with version 2, where
> the order of the "sections" is no more important.
I think this is over-complicating things. Why not just find the file the
way vim handles it's .vimrc:
First check for ./.fvwmrc, then ~/.fvwmrc, then system.fvwmrc. The first
one it finds is sourced, and the rest are ignored.
Yours etc,
Matthew Estela /Z/Z/Z/Z/Z/Z/Z/Z/Z/Z/Z/Z/Z/Z/Z/Z/Z/Z/Z/Z/Z/Z/Z/Z/Z/Z/Z/Z/Z/Z/Z/
mestela_at_progsoc.uts.edu.au
http://www.progsoc.uts.edu.au/~mestela
--
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 - 21:38:17 BST