Show your i3-wm configs/scripts

Desktop Environments All WMs
12

Those picom rules are nasty. You can test your application with xprop command (at least for X11). It will change your mouse cursor, then click on a window that you want to analyze and you will get a summary that you can use for a picom filter. For example:

~ >>> xprop
WM_HINTS(WM_HINTS):
_NET_WM_DESKTOP(CARDINAL) = 0
_NET_WM_STATE(ATOM) =
WM_STATE(WM_STATE):
		window state: Normal
		icon window: 0x0
WM_PROTOCOLS(ATOM): protocols  WM_DELETE_WINDOW, _NET_WM_PING
_NET_WM_ICON(CARDINAL) =
WM_NORMAL_HINTS(WM_SIZE_HINTS):
		program specified size: 800 by 600
_NET_WM_WINDOW_TYPE(ATOM) = _NET_WM_WINDOW_TYPE_NORMAL
WM_CLIENT_MACHINE(STRING) = *redacted*
_NET_WM_PID(CARDINAL) = 14318
WM_CLASS(STRING) = "Alacritty", "Alacritty"
XdndAware(ATOM) = BITMAP
_MOTIF_WM_HINTS(_MOTIF_WM_HINTS) = 0x2, 0x0, 0x1, 0x0, 0x0
_NET_WM_NAME(UTF8_STRING) = "Alacritty"
WM_NAME(STRING) = "Alacritty"

There are more to these configs but I am no expert to give you a clear guide how to set it. I just set it by trial/error approach.

Edit: One more thing. The names of applications are case sensitive. So a rule 100:class_g = 'alacritty' will not work but 100:class_g = 'Alacritty' will work.

3 Likes