Open swhalemwo opened 3 years ago
user202729
commented
3 years ago Does restarting Plover works? (just to be sure. Plover has the local keymap cache) If it does, then you need to merge pull request #1164 .
Where do you even get the 105 and 66 value from? On my machine...
>>> key_combo.parse_key_combo("Control_L(L)", E._get_keycode_from_keystring)
[(37, True), (46, True), (46, False), (37, False)]What does xmodmap -pk output?
swhalemwo
commented
3 years ago thanks for the suggestion! restarting plover does unfortunately not work. the keycode 105 is what plover believed to be Control_R, which is the control key I use for my control key bindings. 66 is actually Control_L on my laptop keyboard (I use plover on a plugged in preonic). Control_L of my preonic also has the keycode 37, however when I use 37 instead of 66, I'm getting a Hyper+key combination.
in case it is relevant, here is also my xkb config; I have moved from xmodmap to xkb for my keyboard configuration, although I don't really understand the system behind it so it is mostly trial and error.
Summary
Hi,
thanks for this great program, it has greatly increased my joy of writing. However, recently I've encountered an issue with my control key combinations: while previously e.g. {#Control_L(l)} would execute Control+L as expected, it now executes Hyper(L), while {#Control_R(l)} executes Super(L) (this completely breaks my workflow since I'm using Emacs and hence very much rely on Control key bindings). Other key combinations with Alt and Super work as expected. I had a look into
xkeyboardcontrol.py, and found that when I manually "remap" the Control key code from 105 to 66 insend_key_combinations, things work as expected:Reproducing
I'm not sure what caused this problem/how to reproduce, as previously my control keys worked as expected and I don't remember what caused the control combinations stop working. It might be that the interaction of qmk (I'm using a preonic keyboard instead of the laptop internal keyboard) and xkb (which I use to get a Hyper key for non-plover tasks) somehow confuses the modifier mapping in Plover?
Plover Version
Git SHA: d20167f
System
5.10.15-1-MANJARO x86_6, i3, running plover from git clone