On Tue, Aug 12, 2014 at 04:14:56PM +0100, Thomas Adam wrote: > FvwmConsole's socket/pipe handling is completely broken, and in moving a > window, I'm noticing that it's being sent a tonne of broadcast packets for > every ConfigureNotify request occuring. This floods the pipes between FVWM > and FvwmConsole until it can be flused.
I'm not sure I understand correctly what you say. Please confirm or correct: 1. The FvwmConsole server requests events that the client is not interested in. --> Can be fixed by choosing the appropriate event mask. 2. These events are not sent to the client (it cannot handle events anyway, but only lines or text). 3. When a window triggers a configure notify, fvwm does many broadcasts? --> If so, this _must_ be fixed in fvwm. > BAsically, FvwmConsole needs scrapping and replaced with something more > robust for this problem to ever go away. I fail to see why the problem (I'm still not sure what it is) is special for FvwmConsole. After all, all module communication is done through the same library, so why does it affect only FvwmConsole? Ciao Dominik ^_^ ^_^ -- Dominik Vogt
