Summary: | XKB_FIXED_LAYOUT for ergodox? | ||
---|---|---|---|
Product: | Wayland | Reporter: | camalot |
Component: | libinput | Assignee: | Wayland bug list <wayland-bugs> |
Status: | RESOLVED WONTFIX | QA Contact: | |
Severity: | normal | ||
Priority: | medium | CC: | peter.hutterer |
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
camalot
2016-12-07 03:10:38 UTC
hmm, I'm going to say "no" here, mostly because the use-case we were aiming for with this property are devices that are more restricted than some programmable keyboard and where the layout is truly fixed and applying *any* layout is just wrong. In your case here that's not quite the case, it's rather that users program the keyboard to do something else but can that be expected of *all* users? Note that I'm speaking for the general case here, you can override things locally and hope for the desktop environments to do the right thing :) after all, GNOME won't care *why* a keyboard has the fixed layout tag set. I understand. Would the local override take the form of a udev rule that somehow sets that property? look at the top of the 60-keyboard.hwdb file, I think it explains how to do local entries with files in /etc/ (if not, 60-evdev.hwdb does). Then you can just add the entry in a separate file and be done with it, no rules needed as long as you use known match strings. Peter, thank you for the pointer to instructions on how to modify the hwdb keyboard rules. I wasn't aware of that and it will be very useful. Also, thank you for all the other great work you do ensuring that our Linux desktops work well! |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.