-
-
Notifications
You must be signed in to change notification settings - Fork 442
Closed as not planned
Description
Problem description
Some systems don't handle CTRL+space correctly. On my machine, running xev from within termux-x11 -xstartup "aterm", pressing and releasing left CTRL results in the following output:
KeyPress event, serial 32, synthetic NO, window 0x600001,
root 0x511, subw 0x0, time 10088320, (1466,1198), root:(1467,1199),
state 0x0, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyRelease event, serial 32, synthetic NO, window 0x600001,
root 0x511, subw 0x0, time 10089266, (1466,1198), root:(1467,1199),
state 0x4, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
Pressing left CTRL followed by pressing the space bar results in the following output:
KeyPress event, serial 32, synthetic NO, window 0x600001,
root 0x511, subw 0x0, time 10091627, (1466,1198), root:(1467,1199),
state 0x0, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyRelease event, serial 32, synthetic NO, window 0x600001,
root 0x511, subw 0x0, time 10092033, (1466,1198), root:(1467,1199),
state 0x4, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
These are the same except for the time field. This same issue is present in normal termux, and is fixed using the ctrl-space-workaround setting inside the .termux/termux.properties file.
Please include a setting that fixes the same issue.
What steps will reproduce the bug?
Follow the steps above.
What is the expected behavior?
CTRL+space is processed properly, and gives the correct keycodes inside xev.
Metadata
Metadata
Assignees
Labels
No labels