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

Vim-style navigation keys #52

Open
zboralski opened this issue May 30, 2023 · 0 comments · May be fixed by #54
Open

Vim-style navigation keys #52

zboralski opened this issue May 30, 2023 · 0 comments · May be fixed by #54

Comments

@zboralski
Copy link

Is your feature request related to a problem? Please describe.
As a frequent user of 'nap' and someone accustomed to Vim's navigation keys, I find it challenging to navigate without using the 'h', 'j', 'k', 'l' keys. This restriction often disrupts my workflow and reduces my productivity.

Describe the solution you'd like
I propose the integration of Vim-style navigation keys into 'nap'. This feature would allow users to use 'h' to navigate left, 'j' to navigate down, 'k' to navigate up, and 'l' to navigate right within the application. This addition would not only enhance the user experience for Vim users but could also serve as an introduction to these intuitive navigation keys for those unfamiliar with Vim.

Describe alternatives you've considered
One possible alternative could be to offer a configurable keybinding feature, enabling users to personalize their navigation keys based on their preferences. This approach offers flexibility but may demand more development effort.

Additional context
The addition of Vim-style navigation keys aligns with the current trend of integrating Vim keybindings into modern code editors and IDEs, thus meeting the expectations of a significant segment of developers who prefer Vim's navigation scheme. Implementing this feature request could help to enhance the overall usability and appeal of 'nap'.

@jolheiser jolheiser linked a pull request Jun 1, 2023 that will close this 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

Successfully merging a pull request may close this issue.

1 participant