You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
The keysym is produced by XLookupString.
https://linux.die.net/man/3/xlookupstring sounds clear to me: it should honour the shift for the Keysym output, and map to ASCII for the ASCII buffer output...
The XLookupString function translates a key event to a KeySym and a string. The KeySym is obtained by using the standard interpretation of the Shift, Lock, group, and numlock modifiers as defined in the X Protocol specification. If the KeySym has been rebound (see XRebindKeysym), the bound string will be stored in the buffer. Otherwise, the KeySym is mapped, if possible, to an ISO Latin-1 character or (if the Control modifier is on) to an ASCII control character, and that character is stored in the buffer. XLookupString returns the number of characters that are stored in the buffer.
Does it work like advertised? We'd better activate DEBUG_KEYBOARD_EVENTS, but currently we print address of the keysym rather than the keysym!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.