On Sat, 3 Sep 2011, Thomas Adam wrote:
And in your example, the xclock window remains sticky across a restart
because of the fix above.
Sorry, but i sais the contrary inmy last post: the xclock
window DOESN'T get the sticky flag ...
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.
I already gave you my config file. What else do you need?
I put the config corresponding to the test I described in my last post in:
http://www.frenkiel-hure.net/pub/config
you can see there that I restart fvwm with
*FvwmButtons "Restart fvwm" "" Restart
as I already told you.
NB: I'm not using any session manager. Is it the same for you?
I also asked what Linux distrib you are using.
--
Pierre Frenkiel
