Jeroen Wijenbergh

> > As written, I have a tendency to use properties for both read and write access, but I would also be open to any other solution as long as...

I have reverted back to using explicit setters (`set_`) when a function is called under the hood. This seems like this was the intention in the codebase as the only...

> Maybe we should reactivate the (deprecated) Seat.set_keyboard then? And either remove the @keyboard.setter or at least deprecate it? Exactly! I did that already in the wlr 0.17 branch >...

Done! Thanks What about this one? https://github.com/jwijenbergh/pywlroots/blob/575a8168286d4f4f08b2013d8ceab49c151a10e0/wlroots/wlr_types/keyboard.py#L154-L160. Maybe `get_modifier` but that is awkward as the API is `get_modifiers`, `get_modifiers` is awkward too because we already have a `modifiers` property

> I ran a fresh vanilla emacs with that config and this is the result: ~20% cpu with the above config ~2% cpu with `(global-display-line-numbers-mode)` removed > > ``` >...

> @jwijenbergh I've updated the emacs version in the top post. It's not pgtk in my case. Ok thanks! I thought pgtk might be part of the problem, but I...

LGTM?

> The only thing I'm hesitant about now is whether we even need this! > > Having been converted the benefits of xephy/wephyr for testing, log messages are just printed...

Honestly I don't understand the issue. Can you re-test with master branch? Is it related to #4176 ?

Moving is implemented, resizing not yet