On Fri, Jan 05, 2007 at 03:58:47PM +0100, Szabolcs Nagy wrote: > why do you swap with memory copy (in view.c/swap())? > why just changing the pointers (prev, next) not enough?
The reason is that clients, stack or sel might be affected during the swap and it's a pain to keep track of those pointers pointing to the correct data. However, the freeze seems to be related to a side-effect of this swap() thing. My brain is too fucked up today, I have no sane solution right now. Maybe you can do it better, lemme know. Regards, -- Anselm R. Garbe >< http://suckless.org/~arg/ >< GPG key: 0D73F361
