You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I want to use the same default layout for all keyboards, but devices like yubikeys (or barcode scanners, or any devices that pretend to be keyboards) use the US-QWERTY layout. Because my keyboard layout (for real keyboards) is hugely customized, I use a xkb file. My config thus looks like this:
with this config, the yubikey uses the layout described in my_weird_layout.xkb instead of US-QWERTY. I guess this happens because xkb_file gets merged from input type:keyboard into input 4176:1031:Yubico_YubiKey_OTP+FIDO+CCID.
A nice solution for that issue would be for xkb_file to accept an empty value:
I'm aware there are other solutions with the actual config syntax (use a xkb file for us qwerty as well, or configure each keyboard individually), but they're not as nice :)
The text was updated successfully, but these errors were encountered:
The last sentence of the blame-commit suggests that new type configs are intended to overwrite existing configs.
$ git show --summary bd3720585
commit bd3720585e91ae0dfcc4be30149ae4f8f5218174
Author: Benjamin Cheng <ben@bcheng.me>
Date: Mon Mar 25 22:05:49 2019 -0400
Implement input type configs (#3784)
Add support for configurations that apply to a type of inputs
(i.e. natural scrolling on all touchpads). A type config is
differentiated by a `type:` prefix followed by the type it
corresponds to.
When new devices appear, the device config is merged on top of its
type config (if it exists). New type configs are applied on top of
existing configs.
This would be a hacky "solution" but does it work as you expect if you flip the order as such:
I want to use the same default layout for all keyboards, but devices like yubikeys (or barcode scanners, or any devices that pretend to be keyboards) use the US-QWERTY layout. Because my keyboard layout (for real keyboards) is hugely customized, I use a xkb file. My config thus looks like this:
with this config, the yubikey uses the layout described in my_weird_layout.xkb instead of US-QWERTY. I guess this happens because xkb_file gets merged from
input type:keyboard
intoinput 4176:1031:Yubico_YubiKey_OTP+FIDO+CCID
.A nice solution for that issue would be for xkb_file to accept an empty value:
I'm aware there are other solutions with the actual config syntax (use a xkb file for us qwerty as well, or configure each keyboard individually), but they're not as nice :)
The text was updated successfully, but these errors were encountered: