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

[request] Make 'C-movement' behave the same as 'C-hjkl' #5827

Closed
moesasji opened this issue Apr 18, 2016 · 1 comment
Closed

[request] Make 'C-movement' behave the same as 'C-hjkl' #5827

moesasji opened this issue Apr 18, 2016 · 1 comment

Comments

@moesasji
Copy link

moesasji commented Apr 18, 2016

For non-qwerty layouts such as colemak hjkl are not on the homerow, making navigating more painful. Instead of remapping keys I solve that by having an additional keyboard layer that puts the movement keys (LEFT, DOWN, UP, RIGHT) at the qwerty position using an additional modifier key.

This works fine for hkjl movement commands as these are bound to hjkl. However for movement commands that involve CTRL this doesn't always work as expected as for example 'C-down' is not bound to 'C-j', etc. Would it be possible to also bind the CTRL-versions of the movement commands to emit C-hjkl, so that these commands can also be generated using movement commands as would be expected?

For an example where going up and down with movement commands doesn't work, see the pasting transient state.

System Info

  • OS: gnu/linux
  • Emacs: 24.5.1
  • Spacemacs: 0.105.18
  • Spacemacs branch: develop (rev. 5ee970f)
  • Graphic display: t
  • Distribution: spacemacs
  • Editing style: vim
  • Completion: helm
  • Layers:
(html auto-completion emacs-lisp eyebrowse git markdown mu4e org latex
      (shell :variables shell-default-height 30 shell-default-position 'bottom)
      semantic spell-checking syntax-checking version-control)
@github-actions
Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Please let us know if this issue is still valid!

@github-actions github-actions bot added the stale marked as a stale issue/pr (usually by a bot) label Feb 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Mailing list
  
Other
Development

No branches or pull requests

3 participants