Ingo Bürk

I don't know what happened here and whether it was in golangcli-lint or gci, but our code was fine before and now throws cryptic error messages all over the place...

You can use an opacity rule matching `_NET_WM_STATE_FULLSCREEN` on `_NET_WM_STATE@:32a` for this.

Compton isn't really being developed anymore. But this is already possible, see my answer above.

@agauniyal Due to #408 it's a bit tricky. To be safe, it should look something like this: ``` opacity-rule = [ "99:_NET_WM_STATE@[0]:32a = '_NET_WM_STATE_FULLSCREEN'", "99:_NET_WM_STATE@[1]:32a = '_NET_WM_STATE_FULLSCREEN'", "99:_NET_WM_STATE@[2]:32a = '_NET_WM_STATE_FULLSCREEN'",...

Yes, I'm aware now. I don't think it used to be like that when I wrote that comment, at least to my knowledge. Glad people are continuing to work on...

The setup script is somewhat incomplete anyway and misses a few things I use. The reason being that I don't execute this script regularly anymore (I used to to set...

@orestisfl @kgilmer Your names pop into my head as obvious candidates here. I certainly don't want to push anyone, but if this is something you'd be interested in doing please...

First of all thanks for the quite details report, that's great! Unfortunately, this comes from a limitation of how i3 draws decorations and is a »known issue«. Preventing this involves...

> Why would the way that i3 draws decoration be affected by key events? What you're essentially seeing is memory garbage. It can be affected by whatever. > If everything...

> What makes you say that? I frankly don't care much about what specifically causes the garbage memory effects to change, predictably or not. I'm not arguing that there is...