On Wed, Feb 04, 2004 at 01:49:17PM +0000, Mikhael Goikhman wrote: > On 04 Feb 2004 09:42:57 +0100, Dominik Vogt wrote: > > > > On Wed, Feb 04, 2004 at 01:26:41AM +0000, Mikhael Goikhman wrote: > > > 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. > > > > In my eyes, it might be better to do this with 3.0 in order to do > > all the disrupting changes in one release. Users get the feeling > > we are constantly breaking compatibility if we do such changes in > > small doses. Other than that, I have no strong opinion about the > > issue. > > My argument is that I don't think we will have 3.0 in less than three > years, and it would be nice to have the clean solution now.
I think it could be done in 2.7.1 as well. In any case, as long as it's optional in the 2.x series, I have no problem with the change. > As described, > it does not break compatibility, just prepares a user in advance. > As for the future, it is possible that there will be 2.8, or maybe 3.0 > will be mostly backward compatible (like 2.6 is), it can't be predicted. > > > > 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 > > > > By the way, this should definitely allow things like > > > > Test (Version [>|<|>=|<=] 2.5.7) ... > > This may be added. > > A bigger problem is that currently $[cond.rc] (should it be renamed?) > is always Match outside of functions, so TestRc (!Match) never works. > This is a bit problematic for dispatchers, they may want to have "else". Due to the several concurrent sources of input (user interaction, modules, X events and the Schedule queue), a lot of scripting does not work when done outside functions. FvwmIconMan has that problem in its button action syntax. Module input in general is problematic. The Repeat and "+" commands can be dangerous too, probably other commands that I missed too. But I don't know what we could possibly do about it. Ciao Dominik ^_^ ^_^ -- 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]
