The picom error window when there is a deprecated thing in config does not respect setxkbmap -device "$id" -option caps:swapescape or setxkbmap -device "$id" -option or caps:escape (find the id with xinput list), so I can't use capslock as esc to close that window. Is it reading raw keyboard data somehow? Also, it seems if I just logged in and the errors pop up I can press esc and it works but if i close and reopen picom i seem to have issues somehow even with esc.
The picom error window when there is a deprecated thing in config does not respect
setxkbmap -device "$id" -option caps:swapescapeorsetxkbmap -device "$id" -option or caps:escape(find the id withxinput list), so I can't use capslock as esc to close that window. Is it reading raw keyboard data somehow? Also, it seems if I just logged in and the errors pop up I can press esc and it works but if i close and reopen picom i seem to have issues somehow even with esc.