>>>>> "Michael" == Michael Han <[EMAIL PROTECTED]> writes:
Michael> On Thu, Apr 11, 2002 at 04:50:14PM +0000, Mikhael Goikhman wrote: >> >> [snip] >> >> I do think that ~/.fvwm/.fvwm2rc name is bad. >> But it should be supported for some time, of course. >> >> It is bad, because this is a main file, it should not be hidden. >> ~/.fvwm directory (or /use/share/fvwm for this purpose) is for fvwm files >> only, so having .fvwm prefix is redudant. And "2". >> >> Something like ~/.fvwm/config or ~/.fvwm/main would be ok. >> >> I am not against (although I think it is not needed) if we introduce an >> extention for fvwmrc files. I.e.: ~/.fvwm/main.fvwm or ~/.fvwm/main.fc. >> >> Any of the suggested names above (or similar) would be good for me. Michael> For many years now I've placed my config in .fvwm/ and invoked fvwm2 Michael> with "-f $HOME/.fvwm/main". This always made better sense to me. And I've always had a fairly simple single file ~/.fvwm2rc (and ~/.fvwmrc before that), it makes more sense to me and I like it that way because it's just like the rc files for my shell, XEmacs (although they are trying to change that as well), etc. Just my personal prefence, and I'd be a little saddened if that method for holding the config info were no longer supported (of course, I'd get over it pretty quickly). I'd argue against the removing of the '2' from the names of the executable and config files since there may be some sites that still have the "ancient" version still lying around and I feel that it helps distinguish it for them, but I guess it's been long enough now that those kinds of situations should be few and far between. :) Chuck -- Charles K. Hines <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Principal Scientist at ReQuest Technologies Inc (http://www.ReQuestTech.com/) "You tell him and I will smack you. I will smack you like a bad bad donkey, okay!" - Pepe in 'Muppets From Space' -- 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]
