You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some keys defined in xah-fly-key-map do get translated (C-o), others do not. Check out <f1> k C-S-o.
It would make total sense to translate, e.g., r (forward-word). In fact, it would make sense to translate every movement key.
I don't know what is the reason. We end up inheriting binding of R as self-insert-command from global-map. I looked at definition of esc-map where keys like b and f get translated properly and found no difference between it and xah-fly-key-map. make-keymap vs make-sparse-keymap makes no difference. It looks like an inheritance issue.
The text was updated successfully, but these errors were encountered:
Some keys defined in
xah-fly-key-map
do get translated (C-o), others do not. Check out<f1> k C-S-o
.It would make total sense to translate, e.g.,
r
(forward-word
). In fact, it would make sense to translate every movement key.I don't know what is the reason. We end up inheriting binding of
R
asself-insert-command
fromglobal-map
. I looked at definition ofesc-map
where keys likeb
andf
get translated properly and found no difference between it andxah-fly-key-map
.make-keymap
vsmake-sparse-keymap
makes no difference. It looks like an inheritance issue.The text was updated successfully, but these errors were encountered: