On Thu 2018.11.01 at 13:18 +0100, Andre Stoebe wrote: > Hi, > > I know this little bug is pretty trivial and more so pedantic, but I > wanted to report it nonetheless and especially ask for confirmation from > other cwm users. It would be great if anyone could try to reproduce.
Hi Andre, I can confirm what you are seeing; it's not intentional; it's mostly because the client (xclock here) sets its border and calculates the x/y position to hand off to the window manager - it doesn't know that the wm is going to rip out the border (with 'ignore' keyword) thus with a default client border of 1, the offset is 2. The client is told its new border width once the window manager sets it, which is why you see it as 0 after-the-fact; but it's too late. This is only a "problem" when east and/or south edge placement is requested. I'm sure someone has noticed this before, right? But if so, I've yet to fix it :) It's good reminder though! Basically we need to carry the original border width around. I'll look to a complete fix. Thanks, Okan
