>>>>> "Mikhael" == Mikhael Goikhman <[EMAIL PROTECTED]> writes:
Mikhael> On 11 Apr 2002 16:34:49 -0400, Charles Hines wrote: ... >> 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). Mikhael> There are several independent things. Mikhael> 1) ~/.fvwm directory is required. We need a search directory for fvwm Mikhael> itself, FvwmM4, FvwmCpp, FvwmForm and just everything else. There are Mikhael> at least 10 scripts and modules wanting to write to the home Mikhael> directory, they all should write to ~/.fvwm, like FvwmAnimate, Mikhael> FvwmConsole, FvwmForm etc. FvwmConsole is a current violator and Mikhael> should be prosecuted. Mikhael> 2) It is not technically rc anymore, we have a full dynamism, when Mikhael> there is no separation between static rc and dynamical commands. Oh, I understand the reasoning for it, as fvwm is not quite as simple as it once was (another thing that saddens me slightly). But I still use it in a simple manner (my only module is the pager really) so I have no need for whole directory structure initialization just yet. Mikhael> 3) A solution for you is simple: ln -s ~/.fvwm2rc ~/.fvwm/main Mikhael> Or whatever name we choose. Or invoke via a shell script called fvwm2 that calls 'fvwm -f ~/.fvwm2rc', or simply give in and go to the new setup or not upgrade my installation (won't happen, just a "for instance"). As I said, 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. :) Mikhael> Removing of the '2' from everything except for executable and fvwm2rc Mikhael> was decided in 1999. It is only a question of time when to complete Mikhael> the task. Mikhael> I am not sure whether you said "yes" or "no", but it is too late. :) Honestly, I don't have any strong feelings on the renaming or using multiple config files in a directory instead of a single rc file, as I'm adaptable (and my rather simple setup probably won't be affected much)...I was just in a wierd mood yesterday and decided to pipe up on this subject. :) And since I believe most of the major Linux distributions have dropped fvwm entirely to make room for more KDE and Gnome stuff (which does more than sadden me), I doubt that they'll be affected by the name change either. Mikhael> I already changed "fvwm2" in your AUTHORS description to Mikhael> fvwm-2.0.x. :) Ah, it's definitely too late then! :) Later, 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]
