-
-
Notifications
You must be signed in to change notification settings - Fork 40
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
equal symbol is not working #20
Comments
update, I tried unchecking all the layout options in the GUI, and revert to the most vanilla us standard keyboard. Then proceed to activate the extend option, and this alone produces the bug above. This should rule out any complicated iteraction of layout and option as source of the problem. |
Any suggestion on how I could proceed to debug this issue? The extend file looks fine, nothing special in the definition of the |
As you say, there's nothing strange about the Extend entry for the equals key (key ) that I can see. If you comment out the lines in that entry alone, the problem appears? How about if you swap key codes between that line and another that's currently working for you? Could you try that out please? Bear in mind that to reset the xkb options you should open with an empty option string, like this: |
I'm using the extend layer option, after installing the xkb files on my system. All seems to work well on most applications, but the extend layer appears to break my "equal" symbol. The key doesn't produce any output on any of my applications. Strangely, the second level of the key, "+" works fine.
Looking at the output of
xev
I see that the key press event is not triggered, instead something else calledKeymapNotify
:And here is the output of
xev
for the shifted version, that produces a+
without problem:The text was updated successfully, but these errors were encountered: