search

alols / xcape

Linux utility to configure modifier keys to act as other keys when pressed and released on their own.
GNU General Public License v3.0
2.1k stars 115 forks source link

Out of bounds F keys #116

Open 5HT2 opened 4 years ago

5HT2 commented 4 years ago

I'm using xcape -e 'Caps_Lock=Escape;Super_L=0xffd4', the keysym for F23 is 0xffd4, as shown by /usr/include/X11/keysymdef.h xcape doesn't recognize it and instead throws WARNING: No keycode found for keysym 0xffd4 (0xffd4) in mapping Super_L. Ignoring this mapping. Is there another way to map it to F23 like keys?

aplotor commented 4 years ago

bump. same issue, F13 onwards

rybern commented 4 years ago

Same issue, trying to map F20

brentgreeff commented 4 years ago

Same issue - I want to map Shift_R=XK_F19 Invalid key: XK_F19 Failed to parse_mapping

AkashaP commented 4 years ago

It's just F13-F24, remove the XK prefix, as per man xcape you can use the macro labels minus the XK prefix

xcape -d -e '2=F13'
Assigned mapping from "2" ( keysym 0x32, key code 11)
to "F13" (keysym 0xffca, key code 191)
sig_handler running...
Intercepted key event 3, key code 36
Intercepted key event 2, key code 11
Key pressed!
2Intercepted key event 3, key code 11
Key released!
Generating F13!
Ignoring generated event.
Ignoring generated event.

I'm having a separate issue though that as a receiver event it only generates the events once and then never works again (e.g F13=2), unless i do something like "F13=2;F13=2" then it works but types twice i am still experimenting with it and posting it as a separate issue

toothbrush commented 4 years ago

I'm getting the same issue, trying to run xcape -e "Super_L=Multi_key". I've checked in xorgproto-2019.1's include/X11/keysymdef.h, and i can see the line #define XK_Multi_key 0xff20. What could be the problem?

The output xcape gives is:

WARNING: No keycode found for keysym Multi_key (0xff20) in mapping Super_L. Ignoring this mapping.
Failed to parse_mapping