r-c-f

@emersion The `margin` properties are supposed to be the standard, but prior to https://github.com/torvalds/linux/commit/6c4f52dca36f5e3e2354c30591d38e92f4657ed9 in 2018 they were intended for SDTV connectors only. i915 continues to restrict `margin` to SDTV...

The keycodes file will just let you specify a different include in `xkb_keycodes` section in the map produced by `setxkbmap -print`; you'd just put `win` instead of `evdev`, for example....

In theory this sort of setup is quite possible; I did it for while with greetd. That being said.... By default, SDDM itself doesn't even use Wayland, so the standard...

In this case, ``` backend = kde [tls] enable = true tofu = true [log] level = debug ``` would cover everything given. I've added the configuration option names to...

Here the corresponding debug log bits for barrier on the server side would be useful, at least for now (I should probably add a provision for more information to the...

`waynergy --loglevel debugsyn` should now present the relevant information in latest master, though it's useful to know that barrier doesn't think it's sending a duplicate at least.

For some reason Barrier is duplicating the button, while sending with a key id of 0, which probably shouldn't be happening. In any case, a workaround. In new latest master,...

Sorry for the delay in response.... In any case, for a simple offset error, you can set `offset` under `[raw-keymap]`. Though I'm glad you got it working the meantime; I'll...

Sorry for the lack of an initial response (this seemed to slip through the email cracks as it were) I'll definitely be having a go at reproducing this. The error...

Looking at sway's debug logging, this is due to xkbcommon 1.5's restrictions on user configuration for even slightly-privileged processes. https://github.com/swaywm/sway/pull/7326 fixes this.