-
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 input.xkb_file option #403
Comments
Can you elaborate why this can be useful? |
Oops. accidentally closed. |
Duplicate of #418 |
Not sure if this is a separate issue, but why does Wayfire's input section read libinput events instead of using the xkb keycodes like sway (and others?) do? This makes it easier to use different keyboard models without having to change configuration files. For example, the chromebook xkb_model can use Wayfire already uses libxkbcommon, so I wonder if there's any reason for the current behavior? |
There is a reason, by using the keycodes we can have bindings which work independently from the current layout (a problem when you have multiple languages). We could in theory have a separate xkb context with a separate set of options for bindings, however so far you are the first one to request that :) |
Sway has a
|
No description provided.
The text was updated successfully, but these errors were encountered: