Re: FVWM: Addendum to FAQ 4.3
On 12 Sep 2002 09:03:08 +0200, Eric Doenges wrote: Mikhael Goikhman wrote: If you insist not to use any 2.4.x features, we can't help. The support on this list and the FAQ (not counting some non-updated parts) is for 2.4.x. [ ... ] Yes, I forgot to mention that for -lock to work you should run: ModuleSynchronous FvwmM4 -lock file This works, thanks. Maybe this tidbit of information should be in the FAQ ? I hope someone will do this. 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]
Re: FVWM: Addendum to FAQ 4.3
On Thu, Sep 12, 2002 at 11:35:24AM +, Mikhael Goikhman wrote: On 12 Sep 2002 09:03:08 +0200, Eric Doenges wrote: Mikhael Goikhman wrote: If you insist not to use any 2.4.x features, we can't help. The support on this list and the FAQ (not counting some non-updated parts) is for 2.4.x. [ ... ] Yes, I forgot to mention that for -lock to work you should run: ModuleSynchronous FvwmM4 -lock file This works, thanks. Maybe this tidbit of information should be in the FAQ ? I hope someone will do this. Do you have anyone particular in mind with someone? I didn't really this thread, but I suspect that unless someone is you, nothing will happen. Bye Dominik ^_^ ^_^ -- Dominik Vogt, [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] -- 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]
Re: FVWM: Addendum to FAQ 4.3
Dominik Vogt [EMAIL PROTECTED] writes: On Thu, Sep 12, 2002 at 11:35:24AM +, Mikhael Goikhman wrote: On 12 Sep 2002 09:03:08 +0200, Eric Doenges wrote: Mikhael Goikhman wrote: If you insist not to use any 2.4.x features, we can't help. The support on this list and the FAQ (not counting some non-updated parts) is for 2.4. x. [ ... ] Yes, I forgot to mention that for -lock to work you should run: ModuleSynchronous FvwmM4 -lock file This works, thanks. Maybe this tidbit of information should be in the FAQ ? I hope someone will do this. Do you have anyone particular in mind with someone? I didn't really this thread, but I suspect that unless someone is you, nothing will happen. I think a man page update is called for. I'll see what I can come up with. -- Dan Espen E-mail: [EMAIL PROTECTED] 444 Hoes Lane Room RRC 1C-214 Phone: (732) 699-5570 Piscataway, NJ 08854 -- 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]
Re: FVWM: Addendum to FAQ 4.3
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]
Re: FVWM: Addendum to FAQ 4.3
On 11 Sep 2002 15:41:08 +0200, Eric Doenges wrote: Mikhael Goikhman wrote: 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. I found that out the hard way shortly after sending my mail (everything seemed to work for me, but broke for some other users =8^(. Fortunately our configuration only uses HOME and USER, which fvwm can expand itself from $HOME and $USER. The real solution to your synchronization problem is to invoke FvwmM4 with the -lock switch. We currently run fvwm-2.2 and fvwm-2.4 (on different Unix variants), but want to have the same configuration files. If you insist not to use any 2.4.x features, we can't help. The support on this list and the FAQ (not counting some non-updated parts) is for 2.4.x. '-lock' seems to be a feature added in version 2.4. Also, if I use '-lock' to read m4-processed files from a .fvwm2rc File, it doesn't seem to do anything (i.e. FvwmM4 -lock file exhibits the same problems FvwmM4 file does). The manual page says to start the module with 'ModuleSynchronous, but the FvwmM4 module itself isn't started anywhere. Yes, I forgot to mention that for -lock to work you should run: ModuleSynchronous FvwmM4 -lock file 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]
