On Sat, Sep 03, 2011 at 07:30:03PM +0200, Pierre Frenkiel wrote: > Can the differences in behaviuor come from the Linux distrib? > Which one are you using?
How are you restarting FVWM? In 2.6.2, I fixed a problem in restoring states with recapturing windows due to WM_COMMAND: https://github.com/ThomasAdam/fvwm/commit/afd732a1a01c9ad71e0a160fd3deac2ec7471753 And in your example, the xclock window remains sticky across a restart because of the fix above. The only thing I can think of is how you're restarting FVWM. Did you send through your config? I mean, all of it, including any stray files which are read via the Read command, etc? There's always the possibility it's still being reset by something which you've not shown me, of course. -- Thomas Adam -- "Deep in my heart I wish I was wrong. But deep in my heart I know I am not." -- Morrissey ("Girl Least Likely To" -- off of Viva Hate.)
