which-key.nvim

Even as a fairly confident nvim user, I still use and recommend <https://github.com/folke/which-key.nvim>

I 100% agree, but I also think you can get very far with just taking a weekend to read the user manual (:h user-manual). It won't solve the remembering problem, but it will make looking up help when you need it much easier. For example, you would know that most window operations start with <C-w>, so when you need to tile windows you could start with looking up `:h ctrl_w`. There is also a very popular plugin for neovim that shows a popup with possible keybinds and descriptions whenever you begin any keybind: https://github.com/folke/which-key.nvim

folke/which-key.nvim: https://github.com/folke/which-key.nvim : > Customizable Layouts: choose from classic, modern, and helix presets or customize the window. LazyVim keymaps: https://www.lazyvim.org/keymaps

> Exactly! Pity this basic contextual help isn't more widespread, every single app that uses a lot of keybind sequences could benefit from it, especially if it becomes a bit smarter and only shows a popup if you don't finish the sequence right away I've been using Vim/Neovim for 20 years, but still can't get enough of which-key[1] which I only installed ~6 months ago. 1: https://github.com/folke/which-key.nvim

If you only wanted to use that feature, you could install the whick-key plugin that LazyVim uses: https://github.com/folke/which-key.nvim

kickstart.nvim [1] is the best way to get started if you want to understand how things are configured rather than using someone else's config. It's a single file and you can pretty easily use it as a starting point for your own config. And it comes with the which-key.nvim [2] plugin that helps you learn vim motions. [1]: https://github.com/nvim-lua/kickstart.nvim [2]: https://github.com/folke/which-key.nvim

There is a well known plugin for neovim to do this kind of behavior. You can even create your own hotkeys into that plugin and will help you navigate and memorize different hotkeys for the editor. The plugin is called whichkey, and this is their github https://github.com/folke/which-key.nvim

One of the innovations in the Vim space that I've appreciated a lot is which-key by folke for Neovim: https://github.com/folke/which-key.nvim It makes keybindings in vim discoverable, it's quite magical. For example, press g and get a table of all the various commands that follow from there. Press mapleader and get a table of various commands from there, etc. Edit: On closer look, I've learned that maybe vim-which-key came before that, and guide-key before that etc, there's a long lineage of this too!

>The problem with that is that for some rarely used action one forgets... Install https://github.com/folke/which-key.nvim and you will always have a popup that will tell you what keys to use next.

My biggest complaint is probably that it doesn't support overlay or popup windows, which makes it impossible to use plugins like WhichKey[0] and such, which I like on normal neovim because I'm a scrub and don't know vim hotkeys by heart 0: https://github.com/folke/which-key.nvim

If you're using Neovim you want this one: https://github.com/folke/which-key.nvim New nvim api lets mappings add a desc which will get picked up automatically with this plugin.

Think what you're asking for is a vim interface built around arbitrary mouse usage and discovery, the latter being of utmost emphasis I presume. And yeah, it's a valid complaint that vim GUI implementers seem incapable of getting to that level and just put chrome around what is essentially a TUI instance. Lack of mouse-led discovery likely also contributes to vim veterans being surprised that vim has this or that feature. TUI-orientation is quite tenuous when it comes to discovery of behavior. The whichkey family of plugins[0][1] is an interesting experiment in combatting this, but does nothing for the large case of commands that aren't mapped to a key by default, like the example of the 'earlier' command mentioned higher in this thread. [0]https://github.com/folke/which-key.nvim [1]https://github.com/liuchengxu/vim-which-key

I've been using vim (neovim) for more years than I can count, but there is still so many movements that doesn't stick in my head, probably because I don't use them so much. I recently came across the which-key.nvim (https://github.com/folke/which-key.nvim) neovim plugin, which helped me a lot to speed up finding what movement I want to do. It basically shows you a popup with what combinations are possible after you press any key (while nvim waits for the next one), so you can basically explore commands by just pressing keys, instead of having to look them up.

> An user friendly editor should pop some kind of prompt when I pressed the first g/G key and show me what I could press the next, See vim-which-key [1] and which-key.nvim [2] for something similar to this. [1]: https://github.com/liuchengxu/vim-which-key [2]: https://github.com/folke/which-key.nvim