linux: wayland: correct whitespace and nullbyte at the end of the keymap #386
Conversation
This file contains 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
Compositors such as labwc expect the keymap to follow a strict format. The whitespace is important and it needs to end with a null byte. Otherwise the length of the received keymap does not match the length of the expected keymap and there is an error.
pentamassiv
force-pushed
the
wayland_keymap
branch
from
83edd9d to
fa043a1
Compare
Draft
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Compositors such as
labwcexpect the keymap to follow a strict format. The whitespace is important and it needs to end with a null byte. Otherwise the length of the received keymap does not match the length of the expected keymap and there is an error.