Enable numlock on start up support

[otaj]

Hi, thank you for the amazing compositor! I use it as a minimal compositor to run regreet for a small login manager. However, I'd appreciate, if it would be possible to enable numlock automatically on start up as I make frequent use of numeric keyboard if it's available. Yes, I can enable it myself, however I often forget about it and then have to try login twice.

Thanks a lot!

[joggee-fr]

@otaj
Do you know which backend you are using when running Cage (DRM, Wayland, X)?
Is it possible to manage numlock activation in the script (or systemd unit or idk) starting Cage? Activating numlock on bootup from ArchWiki.

[emersion]

Ideally we'd provide a way (CLI flag or protocol or config file or something else) to configure input devices and this would be part of it...

[joggee-fr]

@emersion, is it related to issue #138 (and possibly also issue #252) ?

[emersion]

Yup.

[otaj]

@joggee-fr: I'd expect either DRM or Wayland. Definitely not X. However, configuring input methods is a responsibility of a compositor under Wayland - therefore, to answer your second question, even if I set it up at startup, compositor (in this case Cage) "overrides" it.

For some reason, wayland does not have any protocol for managing input devices, such as setting keyboard configuration. @emersion, therefore that means that protocol is a no-go, since AFAIK there isn't any. Sadly, this interesting project doesn't have support for numlock as well. So the only remaining option is to either use env variable, CLI flag or config file.

[otaj]

Umm, the closing was unintentional, reopening again

[emersion]

For some reason, wayland does not have any protocol for managing input devices, such as setting keyboard configuration.

It's not a no-go, it's just a bit of work. Wayland did not have a protocol to configure output devices until we added one.

[otaj]

For some reason, wayland does not have any protocol for managing input devices, such as setting keyboard configuration.

It's not a no-go, it's just a bit of work. Wayland did not have a protocol to configure output devices until we added one.

That's a fair point and to be honest, it might have been the best possible option in the long run, since then the input configuration would be compositor-independent. On the other hand, I have 0 experience with proposing and implementing wayland protocols