Summary: | "send keyboard input" > doesn't send unicode characters (or sends in wrong encoding) | ||
---|---|---|---|
Product: | [Unmaintained] khotkeys | Reporter: | Shual Kravot <as.afgre.enberg> |
Component: | general | Assignee: | Michael Jansen <kde> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | ||
Priority: | NOR | ||
Version: | 5.18.4 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
See Also: | https://bugs.kde.org/show_bug.cgi?id=427682 | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | my khotkeys |
Description
Shual Kravot
2020-10-10 09:55:46 UTC
I just realized the main issue: When I assign Unicode keyboard input to a hotkey, the characters are not sent correctly. I assume they are being sent in plain ASCII, and the unicode char is being interpreted as a control character, (cause random phenomena on the way). How to reproduce: 0. in "Custom Shortcuts", 1. define a keyboard action (New > Global Shortcut > Send Keyboard Input") 2. assign a shortcut key (I tried Meta+M, Meta+W, alt+ctrl+N) 3. assign a non-ascii, unicode string (I used €, or ₪) 4. Save. 5. the keyboard input is not sent 6. when I press the shortcut, I see a brief flicker in the whole GUI/screen, or a random action of the window manager (e.g. raising windows, change task, minimize/maximize, etc). 7. the settings appears in ~/.config/khotkeysrc , and seems "in order". I.e. the character is saved there as UTF-8. I tested the same with pure textual (a-zA-Z0-9) ASCII string, and it worked as expected. Hence I deduce this is an encoding problem, either in the sending part, or the receiving part. Moreover: 1. I created an executable script using xdotool (apt install xdotool) #!/bin/bash xdotool type € 2. This script works as standalone, e.g. from the command line, crontab. It sends the euro character to the active window. 3. If the same script is running by khotkeys's "command/URL", then the outcome is not sent (produce the flicker / actions I mentioned described above). *** This bug has been marked as a duplicate of bug 427682 *** |