AppFlowy
AppFlowy copied to clipboard
AppFlowy-IO
[FR] Vim-like Bindings/Movements
Description
Adding a Vim-like bindings option to allow more powerful keyboard focused controls, and easier use for Vim and Neovim users (or anyone using these controls in other softwares).
This should, in my opinion, be disabled by default, as most users aren't familiar with Vim-like bindings, but be available as an option (probably in the Shortcuts settings?).
Impact
This would be beneficial for:
- Vim/Neovim users who want to use AppFlowy.
- Anyone used to Vim-like bindings integrated in other apps.
- Anyone who wants a powerful keyboard focused workflow.
Additional Context
As someone who mainly works using Neovim, having to edit text without these controls feels awkward and slow to me. I really like what AppFlowy proposes, but my experience would be much better if I had the ability to choose what controls I'm comfortable with, i.e. vim-like bindings. I think this must be a common use case, as I see other applications doing exactly that, either as a plugin, or a feature within the app.
@Sharkitty , have you tried customizing your keybindings through our shortcut menu:
You can change the default shortcuts to your preference.
@Sharkitty , have you tried customizing your keybindings through our shortcut menu:
You can change the default shortcuts to your preference.
I'm aware of that, but vim bindings work very differently, so this would not provide the expected behavior.
@Sharkitty I think this would need to be done within the editor. Which is a separate component of AppFlowy. I did have some luck in getting the h, j, k, l keys working on my own fork of AppFlowy Editor. As for the extra Vim like keys well it just needs some research...
Having good normal mode navigation would be great for keyboard-centric workflows!
I've been missing that in every knowledge I've tried so far (Notion, Obsidian, Loqseq, ...), and that usually makes it pretty hard to properly organize information.
This issue is a duplicate of #284 which was added to the roadmap recently. You can watch progress on this feature there. I suggest closing this issue as duplicate.
