Open
Conversation
Contributor
|
I think you should also specify which variants of azerty this works for (There are a couple) |
|
Hi, I'm from the same indigenous people like you, just another tribe. Please checkout my PR it should be of help. It resolves keybinds to physical keys instead of dynamic names. You can still go back to how it was and use keycode:{num} instead of keysym for keybind assignment. Ex. Mod+Shift+keycode:41 |
Using the power of github.com/Denperidge/xkb-azerty/ this commit adds a separate page for azerty configuration thats wildly complete
Author
|
@ToxicMushroom Variants should be all accounted for! Required putting it on a different page though |
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
3 participants
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.
Hi! I love using Niri and apparently also love using a keyboard layout with a low usershare.
The default keybinds do not work for Azerty, and requires some digging using wev (or a similar tool) to find the equivalent keynames.
So here's a workaround! A docs addition that documents the correct keynames, and has a copy-paste azerty version of the default keybinds