Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Movement keys are not translated #43

Open
akater opened this issue Mar 3, 2018 · 0 comments
Open

Movement keys are not translated #43

akater opened this issue Mar 3, 2018 · 0 comments

Comments

@akater
Copy link
Contributor

akater commented Mar 3, 2018

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant