You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Compose files are read by libxkbcommon not kitty directly. You should file the report against that project. (I long ago removed the default glfw key handling and replaced it with libxkbcomon as glfw does not support dead keys at all, among other problems).
Oh, if you’re handling this in libxkbcommon, then the compose file parsing is likely not an issue, since I know that other libxkbcommon-based applications support these sequences. I think the issue might be with glfw_xkb_handle_key_event. The function assumes that the input is not yet complete unless there’s a keysym. However, for multi-character sequences defined without an associated keysym, it looks like this does not have to be true.
When I apply the following, it shows me that key_event.text is ♪┌|°з°|┘♪ └|°ε°|┐♪ ┌|°з°|┘♪, so the compose lookup seems to work. The issue is just that it’s not used as input.