-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wayland/GDM/Gnome doesn't support 5th level (with <> key) #3
Comments
Hey, thx for trying it out :) I'm currently using X, so maybe its related to that, but have you already had a look at this part of the readme and maybe the linked Neo FAQ there? And by enabling it with setxkbmap you mean something like |
Heya, sorry for the delay, I was expecting answers to my issues to send me an e-mail. Anyway, I tried the I also do remember having to set an option in the Tweaks application, namely the For now, I am using ch+fr_nodeadkeys, with the neolight:escape_keys option configured with the help of dconf, but the I checked the section of the readme, but this only seems to be adressed to people having multiple keyboard layouts? I only have |
Update: I just tried the |
I just got a new machine and am using wayland now as well. Same issue as you :/. So it does seem to be wayland-related. I'm going to look into it in more depth soon and hopefully fix it.
Oh, I didn't know it's possible to modify those entires. I'll try adding them.
You are right, if you only have one layout anyway it's not relevant. |
The reason seems to be this: xkbcommon/libxkbcommon#18 (I'm using "RedirectKey" in the layout). Also no good workaround yet it seems: xkbcommon/libxkbcommon#145. I'll try to do it without RedirectKey, like neo does, but this caused issues in the past in some applications (e.g. not properly recognizing the arrow keys, or interpreting them as someModifier+arrow). But maybe most of them have improved their keyboard handling by now. |
Aha! I see. Glad you found the issue! Lemme know if i can help in any way, I'd be more than happy to! (even tho i'm fairly new to the Linux universe...) |
Alll right, found the time to work on it again. It should work on Wayland now. And happily, every application that previously had issues is working even without the RedirectKey (except for Sublime Text initially, but I found a good solution). Also the options show up in gnome-tweaks now. I'll update the readme and release a new version in a while. In the meanwhile, if you want, it would be helpful if you could test if everything works now :) |
sorry, was on holiday so i didn't pay any attention to github ^^' Just tried it out and it works like wonders! Also just tried the new locking feature, works perfectly as well! thanks for your reactivity! I would love to help you in that project but I have no idea how to work with all the stuff in this repository ^^' |
Thanks for testing! I've released the new AUR package now (in case you are using archlinux). Yeah, unfortunately the whole xkb configuration is particularly arcane and complicated. I've spend more hours and days on it over the years than I care to admit. Luckily there now is https://xkbcommon.org/doc/current/xkb-intro.html, which brings some amount of sanity at least to the documentation. One thing that is missing is making the xkb-options work for other layouts than just the first. This issue gives some pointers on what is going on: xkbcommon/libxkbcommon#97 (comment) (starting from "This rule only applies to the first group, ..."). Maybe something like
put here would already work? If you ever feel the urge to work on this, let me know and I can give you some more pointers if you want. |
i'll take a look this evening. I'll open a related issue (#4) and post updates there accordingly |
I just installed this package on my Wayland - GDM - Gnome setup, but it doesn't seem to support the 5th level. I enabled the option in dconf, and the caps lock works for special symbols, but the <> key doesn't, for the navigation keys.
When i enable it with setxkbmap (with the help of Xwayland), it does work, but it's not ✨ clean ✨
Thx for you attention, will keep you updated if i figure out anything else
The text was updated successfully, but these errors were encountered: