Allow VoidSymbol keycode to be seen by wezterm #759
Merged
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.
When using
setxkbmap
to disable the functionality of CapsLock, it shows as0x00FFFFFF VoidSymbol
keycode. That was not being picked up by wezterm.These changes allow it to be picked up as VoidSymbol so the CapsLock key can be used without any unintended side-effects.
This is how
xev
and other applications see it once disabled and could even be used when disabling other keys to have them be used similarly.Makes for a great LEADER independent from anything else without going shift crazy.