On Thu, Jan 02, 2003 at 11:12:06AM +0100, Olivier Chapuis wrote: > On Thu, Jan 02, 2003 at 09:55:22AM +0000, Mikhael Goikhman wrote: > > I have implemented a new conditional command that is unlike all others > > do not work on windows. Currently only several conditions are available, > > but more useful conditions may be added. > > > > On (Version 2.6.*) Echo Ok > > Cond (NoMatch) Echo Not ok > > > > As usual, these lines should be placed in a function for Cond to work. > > > > InitFunction and RestartFunction now may be obsoleted, everything > > could be done in StartFunction and the user chooses the order: > > > > AddToFunc StartFunction > > + I Module FvwmBanner > > + I On (Init) Exec xterm > > + I Module FvwmButtons > > + I On (Restart) Exec play dzin.wav > > + I Module FvwmPager > > > > Thinking about this, if I add SessionInit and SessionRestart conditions we > > may remove even more special functions in the long run. Having totally 2 > > functions StartFunction and ExitFunction instead of the current 8. > > > > Should I mark InitFunction and RestartFunction as obsoleted in the man > > page and/or the code, or we need to support them forever? > > > > The problem is that since 2003-01-01 fvwm/fvwm is feature freezed! > Yes, we do not get a warning message from Dominik ... > Dominik, are you still our maintainer for 2.5.x/2.6.x ?
No. I *may* fix a few bugs, but other than that I do not plan to spend much time on fvwm anymore. > I strongly > hope this. Note that we should fix a date for module feature freeze > and also a date for string freeze (for translation; this involves > fvwmrc discussion). Well, I see nothing that should stop someone else from setting the dates. Bye 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]
