Add determining keyboard layout from Wayland #1807
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
iansw246
force-pushed
the
wayland-keymap
branch
2 times, most recently
from
8d34024 to
aaf3a75
Compare
iansw246
force-pushed
the
wayland-keymap
branch
from
aaf3a75 to
97d2312
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary of changes
Adds a Linux keyboard layout option "wayland-auto" that retrieves the current keyboard layout from the running Wayland compositor. Uses the xkbcommon package to parse the keymap, as well as to generate the other keyboard layout options.
Solves #1726 but only for Wayland users.
Another limitation is that keyboard capture isn't using the retrieved layout. This means keyboard modifiers other than the standard QWERTY keys (for example mapping CapsLock to Ctrl) won't be handled properly when passing through keyboard shortcuts. This issue exists currently so new issues shouldn't be added and this PR should be ready to merge.
Pull Request Checklist
Changes have testsLinux specific changes