[awesome bugs] #1104 - support XLookupString or XKeysymToKeycode
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#1104 - support XLookupString or XKeysymToKeycode User who did this - Daniel Hahler (blueyed) -- It seems like XLookupString or XKeysymToKeycode might solve it, yes. Do you feel like testing it and providing a patch / pull request (via https://github.com/awesomeWM/awesome) for it? -- More information can be found at the following URL: https://awesome.naquadah.org/bugs/index.php?do=detailstask_id=1104#comment4223 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. -- To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.
[awesome bugs] #1104 - support XLookupString or XKeysymToKeycode
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#1104 - support XLookupString or XKeysymToKeycode User who did this - Daniel Hahler (blueyed) -- Well, there's the following in keyresolv.c: /** XCB equivalent of XLookupString which translate the keycode given * by PressEvent to a KeySym and a string * \todo use XKB! */ static unsigned short const keysym_to_unicode_1a1_1ff[] = ... -- More information can be found at the following URL: https://awesome.naquadah.org/bugs/index.php?do=detailstask_id=1104#comment4224 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. -- To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.
[awesome bugs] #1104 - support XLookupString or XKeysymToKeycode
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#1104 - support XLookupString or XKeysymToKeycode User who did this - epegzz (epegzz) -- I tried awesome-git in which FSF177 is supposed to be resolved. Since my issue remains, I guess it aint a duplicate. Someone in #neo on freenode told me, that you are using the neo keyboard layout? (http://neo-layout.org) Then you could verify this issue by trying to use the number keys from layer 4 to switch tags. Or you can try to use Tab, Enter or the number keys in the run-command widget. Neither works. Using keycode 58 in my example would not work for me, because I use this keycode to generate all kind of symbols, depending on which virtual modifier I press at the same time. That's the keyboard layout I'm using: https://raw.github.com/epegzz/coder-layout/master/artwork/de_coder.png But the issue remains the same when I use Neo2 instead of my keyboard layout, with the only difference that with Neo2 I can at least still use the original number keys. Which is most likely the reason why no other neo2 user complaint about this issue before I guess. Using XLookupString or XKeysymToKeycode instead of keycode really would solve the issue, wouldn't it? :-) -- More information can be found at the following URL: https://awesome.naquadah.org/bugs/index.php?do=detailstask_id=1104#comment3434 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. -- To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.
[awesome bugs] #1104 - support XLookupString or XKeysymToKeycode
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - epegzz (epegzz) Attached to Project - awesome Summary - support XLookupString or XKeysymToKeycode Task Type - Bug Report Category - Core Status - Unconfirmed Assigned To - Operating System - Linux Severity - High Priority - Normal Reported Version - 3.5 Due in Version - Undecided Due Date - Undecided Details - Hi! :-) I mapped the numbers from the numbers row to somewhere else on my keyboard. But those new located number keys aren't recognized by awesome as number keys, therefore I am not able to use them for key bindings. Example: 1 mapped to j on a QWERTZ-layout: KeyRelease event, serial 33, synthetic NO, window 0x2a1, root 0xc5, subw 0x0, time 329174121, (566,262), root:(566,281), state 0x20, keycode 58 (keysym 0x31, 1), same_screen YES, XKeysymToKeycode returns keycode: 10 XLookupString gives 1 bytes: (31) 1 XFilterEvent returns: False But Neither using XKeysymToKeycode (#10) nor using XLookupString (1) in the rc.lua works. More information can be found at the following URL: https://awesome.naquadah.org/bugs/index.php?do=detailstask_id=1104 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. -- To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.
[awesome bugs] #1104 - support XLookupString or XKeysymToKeycode
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#1104 - support XLookupString or XKeysymToKeycode User who did this - Uli Schlachter (psychon) -- Could this be a duplicate of FS#1077? Also, I think you want to use #58 in your rc.lua to make this work. -- More information can be found at the following URL: https://awesome.naquadah.org/bugs/index.php?do=detailstask_id=1104#comment3432 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. -- To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.
