Ingo Bürk

> I'm saying that there are multiple bugs involved. Well, fair enough. I'll reopen for now on the assumption that that's correct. However, I won't have time to look into...

FYI, https://github.com/i3/i3/issues/3481 and/or https://github.com/i3/i3/issues/3479 might improve this situation (both open tickets at this time).

The state of each involved issue (this and the referenced ones) can be seen in the issues. The answer is: no, there has not been any recent work.

I'm thinking that https://github.com/i3/i3/pull/4280 could likely fix this. If someone wants to try it out please go ahead and let us know here.

That PR ended up having some issues and got reverted. It's now merged as https://github.com/i3/i3/pull/4336, which means the current gaps-next branch has this included. If the issue persists the hypothesis...

@Tuuuukka No, sorry, for me personally i3-gaps is now purely a "keep it up to date with upstream" project. If someone wants to look into this and can find a...

The root cause here is how i3 draws window decorations, which is on the parent container and not the window itself. I'm tentatively open to fixing this, but if possible...

Thanks for the idea, but (much like upstream i3) I'm not looking to add more features like that into i3-gaps at this point. I'll leave this open for now for...

You'd have to use the gaps data structure on non-workspace containers, which infrastructure-wise is in place. In `calculate_effective_gaps` in `src/con.c` you'd have to change it to look at the gaps...

Thanks for opening this issue. This is indeed a consequence of the i3 rendering process and the stacking order, see duplicate issue https://github.com/i3/i3/issues/3676. You can patch this locally but at...