Enable resolve_binds_by_sym in Hyprland input configuration - #10539
Open
oscarbol09 wants to merge 1 commit into
Open
Enable resolve_binds_by_sym in Hyprland input configuration#10539oscarbol09 wants to merge 1 commit into
oscarbol09 wants to merge 1 commit into
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
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.
The stock touchpad bindings in \default/hypr/bindings/media.lua\ (\XF86TouchpadToggle, \XF86TouchpadOn, \XF86TouchpadOff) never fire on laptops whose EC/hardware emits \KEY_TOUCHPAD_TOGGLE\ (evdev 530 / XKB 538). Because this keycode exceeds 255 and Hyprland's \input:resolve_binds_by_sym\ defaults to \alse, reverse keysym-to-keycode resolution does not reach that range and the bindings remain inactive.
Setting
esolve_binds_by_sym = true\ in \default/hypr/input.lua\ enables Hyprland to resolve these keysym bindings properly.
Fixes #10449