dotfiles VS which-key.nvim

I suggest looking at https://github.com/nvim-lua/kickstart.nvim for your configuration starting point. https://github.com/LazyVim/LazyVim also provides cool preconfigured setup. You can take a look at my https://github.com/kiyoon/dotfiles to see how I configured. I didn't use any of the preconfigured ones.

0.4.3 is too old and yeah you should upgrade. Nothing will crash but first uninstall what you have. Appimage is just like a binary. You can download it and execute it directly. You should put nvim.appimage to somewhere in your path. I've also made a script to do this: script it will install both tmux and neovim the latest version to ~/.local/bin and if you set that to your $PATH environment variable then the installation is done

solution

I'm glad it helped :) I had to do this kind of thing a lot when I configure my neovim. For example, I wanted to use tmux.nvim to sync registers with tmux. I also wanted to use OSC52 so I can copy from remote server to the local computer's clipboard. I wanted to use yanky.nvim so I can cycle through registers when I paste. All of them are mapped to p key. The entire configuration is here

See my dotfiles for how I install the latest neovim, tmux, zsh, and other apps all locally. I also work remotely very often I managed to install everything without sudo.

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

The menu most certainly comes from folke/which-key.nvim. Take a look into part of your config which sets it up.

By default, most of nvim packages have WhichKey plugin which shows popup with available commands. For instance, you press space or g and what for a second:

One of the recent 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.

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

https://github.com/folke/which-key.nvim - it's like a cheat sheet in neovim!

folke/which-key.nvim will help with you with your key maps.

I recently started actively using which-key plugin that shows the contents of all registers when pressing ".

3) I'd recommend using Telescope, more specifically, :Telescope keympas. There's also which-key, which might be more intuitive, but I haven't used it.