I already started this topic several times in the past, but it seems
noone else worries about this. I worry, so I will implement this soon.
In short, ".fvwm2rc" name has 3 small problems as explained in todo-2.6.

I suggested either ~/.fvwm/main or ~/.fvwm/config variants in the past.
The second one seems to be the most intuitive. Also ~/.*/main does not
return anything for me, and ~/.*/config returns 12 application config
files in my home directory.

Currently fvwm searches for the starting config file in 5 places, I will
add 2 more places, i.e. $FVWM_USERDIR/config and $FVWM_DATADIR/config.
Some places (like ~/.fvwm2rc in $HOME) should be removed, either before
or after 2.6.0. Of course, ~/.fvwm/.fvwm2rc should stay for some years.

Another thing I will do later is to go throw all zillions places
containing the string ".fvwm2rc" and replace it with "~/.fvwm/config".
This way we will be completely free from "2" in our file names.

Note that ~/.fvwm/config is designed to be the final fvwm config file.
A user may already dispatch it if he really wants, like:

  Test (Version 2.5.*) Read config-2.5
  Test (Version 2.6.*) Read config-2.6

Regards,
Mikhael.
--
Visit the official FVWM web page at <URL:http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm-workers" in the
body of a message to [EMAIL PROTECTED]
To report problems, send mail to [EMAIL PROTECTED]

Reply via email to