Mikhael Goikhman wrote: > On 19 May 2004 22:31:41 +0200, [EMAIL PROTECTED] wrote: > >> Maybe Debian's patch modifies something - it (the patch) is quite >> large (200 Kb), and though I couldn't find that it modifies >> the code itself, maybe some settings were affected. > > > > Well, this is pretty easy to verify. Download and unpack the sources and > issue these 2 commands, "./configure --prefix /tmp/fvwm; make install". > Then type in FvwmConsole: Restart /tmp/fvwm/bin/fvwm # -f /dev/null
Well, strange things happen... I compiled/installed fvwm as you have said, ran "/tmp/fvwm/bin/fvwm --replace" (from xterm), and everything started working as it should. But then, I killed X, removed /tmp/fvwm and restarted X, being sure that I have found a bug (in the package), but to my amazement everything *still* continued to work (before running newly compiled fvwm, FvwmEvent didn't work, and I didn't touch any config files). I thought that maybe somehow the old fvwm/FvwmEvent were overwritten in the process, but no, "ls -l" shows that it is not the case. I am curious what could have caused it - in order to compile fvwm I had to install a lot of new packages, so maybe it has to do something with that - does fvwm exectuable/FvwmEvent module have some external dependencies which, if lacking, won't prevent them from running, but will cause some features not to work? Don't know what/whether to report it to the maintainer of the package. ddtl. -- 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]
