> > Yes, I did. Copy-paste the following lines into FvwmConsole. They should > work for 2.5.10. > > DestroyModuleConfig FvwmEvent* > *FvwmEvent: add_window Maximize > KillModule FvwmEvent > FvwmEvent >
Still no go. > Is it possible you just destroy StartFunction later in your config? > Are you sure you don't run an incorrect fvwm executable? > No, I don't destroy it - actually, I have added StartFunction function to the config file only for the sake of FvwmEvent module. Also, when I run FvwmConsole (I have a shortcut key for that purpose) it says Fvwm 2.5.10, so it seems that it is a correct executable. > I don't think Debian package may somehow break this. > 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. After all, there should be some reason for that behavior. 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]
