What does HackerNews think of which-key.nvim?

My favorite Vim oneliners for text manipulation | Aug 2023

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!

LazyVim | Jul 2023

>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.

VSCode-Neovim: Use embedded Neovim in VSCode without emulation | Nov 2022

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

Helix: Post-Modern Text Editor | Nov 2022

Expand Context ↕

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.

History and effective use of Vim (2019) | Jul 2022

Expand Context ↕

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

Neovim 0.7 Released | Apr 2022

Expand Context ↕

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.

Micro – a modern and intuitive terminal-based text editor | Nov 2021

Expand Context ↕

> 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

Nvui: A NeoVim GUI written in C++ and Qt | Aug 2021

Expand Context ↕

> Has enough introspektion to allow something like emacs which-keys?

Yes. https://github.com/folke/which-key.nvim

Neovim v0.5 | Jul 2021

Expand Context ↕

which-key.nvim too, plus more features. Really useful for remembering/learning new plugin mappings.

https://github.com/folke/which-key.nvim