vim-which-key

> even though I'm a terminal user ... I really like the discoverability of GUIs, and that's where a good GUI is unbeatable by CLI. CLI has poor discoverability? Sure; but even on the terminal, discoverability can still be good: A couple of nice examples of discoverability in keyboard-focused programs: - emacs' which-key[0]; there's a vim port[1] too. This shows you (some) of the available keybindings for the next input, and a short label. So you don't have to remember what `SPC h p ...` or all the options under `SPC f...`.. but it still helps to recall that `SPC h` is for 'help' related commands, `SPC f` for file related commands. - emacs' magit[2][3]. Magit is so good at discoverability, that I'd rate it as the best tool for using git with. I've learned more about git from using it. [0] https://github.com/justbur/emacs-which-key [1] http

Agreed, that's the only time I find myself missing Emacs' which-key. (Looks like there is https://github.com/liuchengxu/vim-which-key for this.)

Just an extension. It is https://github.com/liuchengxu/vim-which-key if you are interested. >Were you also able to replicate the small popups that open when you press `m`, `g`, etc.? Yes, although 'm' has a totally different meaning in vim (placing a mark), so there is no popup for that. But it works where there are actually sensible choices, even for marks it works and shows you every available one, which is pretty cool

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

> 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