On 11 Sep 2002 09:44:26 +0200, Eric Doenges wrote: > > first a short disclaimer -- I have no idea if this is the correct > mailing list, but there seems to be no other way of contacting the > fvwm maintainers. If this mail is inapropriate, I'm sorry. > > Anyway, I have an addendum to FAQ 4.3 "I'm seeing odd things when > trying to preprocess files with the FvwmM4/Cpp module...". > > I was seeing strange things too. On our setup, the main .fvwm2rc file > reads a number of different subfiles, some of which were parsed with > FvwmM4. This periodically led to a race condition where FvwmM4 was not > finished processing before the M4 output was needed elsewhere in the > configuration (in our case, the problem was with FvwmButtons being > started before the apps to swallow had been started). The fix detailed > in FAQ 4.3 did not help (because we were starting other modules), but > the solution was surprisingly simple: > > I replaced all "FvmM4 <file>" commands with "PipeRead 'm4 <file>'" and > everything seems to work now.
Well, this may be useful, but it is not the same, none of the X and FVWM related constants are expanded, usual search paths are not used and so on. The real solution to your synchronization problem is to invoke FvwmM4 with the -lock switch. Regards, Mikhael. -- Visit the official FVWM web page at <URL: http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
