On 11 Apr 2002 16:34:49 -0400, Charles Hines wrote: > > >>>>> "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).
There are several independent things. 1) ~/.fvwm directory is required. We need a search directory for fvwm itself, FvwmM4, FvwmCpp, FvwmForm and just everything else. There are at least 10 scripts and modules wanting to write to the home directory, they all should write to ~/.fvwm, like FvwmAnimate, FvwmConsole, FvwmForm etc. FvwmConsole is a current violator and should be prosecuted. 2) It is not technically rc anymore, we have a full dynamism, when there is no separation between static rc and dynamical commands. 3) A solution for you is simple: ln -s ~/.fvwm2rc ~/.fvwm/main Or whatever name we choose. > 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. :) Removing of the '2' from everything except for executable and fvwm2rc was decided in 1999. It is only a question of time when to complete the task. I am not sure whether you said "yes" or "no", but it is too late. :) I already changed "fvwm2" in your AUTHORS description to fvwm-2.0.x. :) It was an interesting quest to find a replacement for fvwm2 (if at all) in every single place. But it seems like a nightmare to do the same for fvwm2rc, it is in 90 files. No way, somewhen we should do this. 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]
