FVWM: .fvwmrc file

From: Mr. Graeme McCaffery <mccaffer_at_eee.bham.ac.uk>
Date: Mon, 25 Sep 95 13:34:53 BST

I have mentioned this before, but my wish for fvwm is to have the
DEFAULT config file split into sections, to make it easier for
individual users to change things like style without having to copy the
entire .fvwmrc file. This would make it easier for novice users to debug
faults in their configuration.

Another advantage to this system, would be that it would allow modules
to be written easily by different people, that could change the
configuration of fvwm, in keeping with the modular structure of fvwm.
I reckon that most users already split their files and use M4 or CPP to
sort their files, but this takes a bit of knowledge, so setting it as
standard would help newbies.
For those who already like the one file config, the -f option would
allow them to continue as normal.

I propose a system fvwm directory with

Style
mouse
module
function
popup
etc files

and a home fvwm directory as defaults

the user would then be free to only edit those files as needed and would
save system's admin and fvwm mail lists a lot of hassel.
lots of people do this in practice, I ask that it becomes standard.
-- 
>From Mr. G. McCaffery 
email: G.McCaffery_at_bham.ac.uk
snail mail: University of Birmingham
	    School of Electrical &
            Electronic Engineering
	    Birmingham
	    B15 2TT
--
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 Mon Sep 25 1995 - 07:31:50 BST

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