Fixes: keybind clash detection also correctly detects grave
against mutter Above_Tab
. Fix keybind replace.
#530
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.
This PR fixes several keybind detection issues (one introduced in Gnome 44 support branch).
Keybind detection has been broken for a while - this became apparent in Gnome 44. Branch
fixes-gnome-44-support
found and fixed the root cause of PaperWM not correctly identifying clashes with system keybinds (so that it can override them while PaperWM is active.FIX 1: mutter
Above_Tab
check againstgrave
Mutter uses
Above_Tab
in keybinds, while PaperWM and gnome can also usegrave
, to describe the same button. This fix normalises these references in PaperWM keybind clashes so that clashes involving PaperWM vs. system keybinds involvinggrave
are detected correctly (and overridden where needed).FIX 2:
Above_Tab
internal reference inadvertedly changed to uppercase infixes-gnome-44-support
branchNot sure how (or why), but I changed the internal reference used by PaperWM to uppercase. This inadvertedly broke PaperWM keybind detection (in the PaperWM settings) involving
Above_Tab
.