-
Notifications
You must be signed in to change notification settings - Fork 177
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add per-device keyboard layout support #2481
Labels
Comments
The input config is documented to be in |
soreau
added a commit
that referenced
this issue
Nov 6, 2024
This patch checks for additional configuration sections so keyboards can be matched by name or with udev properties. Running wayfire with '-d' will log the sections that are being checked, for reference. This allows multiple keyboards to be configured differently, whereas before, all keyboards used the common configuration in the [input] section. To be clear, no additional configuration is required. If no matching configuration section is found for the device, [input] options will be used. Fixes #2481.
soreau
added a commit
that referenced
this issue
Nov 6, 2024
This patch checks for additional configuration sections so keyboards can be matched by name or with udev properties. Running wayfire with '-d' will log the sections that are being checked, for reference. This allows multiple keyboards to be configured differently, whereas before, all keyboards used the common configuration in the [input] section. To be clear, no additional configuration is required. If no matching configuration section is found for the device, [input] options will be used. Fixes #2481.
soreau
added a commit
that referenced
this issue
Nov 6, 2024
This patch checks for additional configuration sections so keyboards can be matched by name or with udev properties. Running wayfire with '-d' will log the sections that are being checked, for reference. This allows multiple keyboards to be configured differently, whereas before, all keyboards used the common configuration in the [input] section. To be clear, no additional configuration is required. If no matching configuration section is found for the device, [input] options will be used. Fixes #2481.
soreau
added a commit
that referenced
this issue
Nov 6, 2024
This patch checks for additional configuration sections so keyboards can be matched by name or with udev properties. Running wayfire with '-d' will log the sections that are being checked, for reference. This allows multiple keyboards to be configured differently, whereas before, all keyboards used the common configuration in the [input] section. To be clear, no additional configuration is required. If no matching configuration section is found for the device, [input] options will be used. Fixes #2481.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi! My current setup has 2 keyboards, an external one which I use at home and the laptop one which is used mostly everywhere else.
My suggestion comes from my previous experience with other wlroots compositors:
sway
hyprland
As seen in the examples above, in both compositors you can set keyboard options based on the device names returned by
swaymsg -t get_inputs
and the hyprland equivalent.#2419 could be relevant to this issue.
The text was updated successfully, but these errors were encountered: