Graeme.McCaffery_at_astro.cf.ac.uk (Graeme McCaffery) writes:
> I hope that this request could be considered.
>
> after using CDE for a while (I had no choice and have now resolved this) I fi
> nd that it would be preferable to have a .fvwm directory in home that contain
> s fvwmrc rather than the present situation.
>
> it would be nice if fvwm seached first for $HOME/.fvwmrc
> then $HOME/.fvwm/fvwmrc
>
> and if the second was the case, then set an internal variable FVWMHOME to $HO
> ME/.fvwm
>
> this would make the spliting of a monlithic fvwmrc file an easier task both f
> or users and administrators!
>
> for instance each user would only have to create a .fvwm directory and copy a
> style file to change the colours of windows.
> all other settings would remain unaffected and under the control of the admin
> istrator.
>
> the present behaviour would be unaffected and I'm sure the change would requi
> re little overhead or code bloating.
You can get this without change to fvwm2 by starting fvwm2 with a
shell that supplies the -f argument to fvwm2. In the shell you can
even create the $HOME/.fvwm/fvwmrc files that you want for first time
users.
> Graeme
>
> --
> email: G.McCaffery_at_astro.cf.ac.uk
> --
--
Dan Espen Phone: (908) 699-5570
dane_at_bae.bellcore.com
444 Hoes Lane Room RRC 1C-214
Piscataway, NJ 08854
--
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 Feb 26 1997 - 10:40:29 GMT