On 2012-03-17 22:57:32 +0000, Thomas Adam wrote:
> Use the "-lock" option to FvwmM4. Read up on "ModuleSynchronous" also.
It can be the solution, but I recall when I've said in Message #10:
The FvwmM4 man page suggests to use ModuleSynchronous to imply the
-lock option, thus avoiding (1) (and possibly (2)?), but if locking
is the solution,
* why does the FvwmM4 man page give an example
fvwm -cmd "Module FvwmM4 .fvwm2rc"
if this is intentionally buggy?
* why doesn't FvwmM4 do a systematic lock?
--
Vincent Lefèvre <[email protected]> - Web: <http://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
