samhocevar/wincompose

minor bug regarding the multiocular o (u+a66e) and qmk

yotsashi opened this issue · 1 comments

For the heck of it, I added a layer to a custom keymap exclusively for random symbols. It works perfectly well for most symbols on the keyboard. The only one it doesn't seem to work for is the multiocular o symbol (u+a66e, ꙮ). When I push the button for that symbol, it instead prints ă66e with an extra line after it. And by extra line, I mean that a message will send in discord right after pressing that button.

Tried to go to the qmk discord to fix it. They said it might be a bug here.

This bug is very minor and exclusive to those using the multiocular o on a custom key map in qmk. It still works if I, on a normal keyboard, type alt, o,+

Update: found out that this is due to the hex starting with A. Pressing alt, u, a, 6, 6, e conflicts with alt, u, a, so it prints ă66e and not the intended ꙮ. Can be fixed by removing the conflicting combos or allowing the user to change sequences. And uh, it effects anyone who wants to add a Unicode character that starts with an "a" in the hex in their key map