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 majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Wed Sep 11 2002 - 10:11:21 BST