Direct Unicode input

[mdSlash]

Is your feature request related to a problem? Please describe.
I'm using different apps to control my keyboard layers, and I have non-English Unicode characters in my keyboard layers. I insert them using their Unicode. When I insert a non-English character by its Unicode, Kitty directly leaves the current window and turns me into its Unicode UI window. It inserts the character correctly and then returns me to the same window I was working on. The problem I am encountering is that I don't need that UI window to show, as I mentioned in the discussion #7223.

Describe the solution you'd like
Adding a config option that disables Kitty's Unicode UI, enabling users to insert Unicode directly by code, name, or favorite without leaving the current window.

[kovidgoyal]

Then get your input layer to not send ctrl+shift+u and only send the
actual unicode character.

[mdSlash]

Then get your input layer to not send ctrl+shift+u and only send the actual unicode character.

You closed that issue quickly, and the app I use doesn't support inserting Unicode directly. My problem is still ongoing. Thanks for your help. I will find a solution eventually.

[kovidgoyal]

I'm afraid I have no idea what your issue is. Either your app sends
ctrl+shift+u to kitty in which case you use the kitty unicode picker. Or
get your app to do whatever it wants to do when you press ctrl+shift+u
and send the resulting unicode as a key event to kitty. If your app is
not capable of doing that, I suggest finding a better one. Typical
candidates are: XCompose, IME via obus or fcitx or similar.