dotfiles_skeleton VS which-key.nvim

You can also use my dotfiles skeleton to see, if you have different demands. https://github.com/matu3ba/dotfiles_skeleton

Personally it would have helped me to start outright with version tracking and documenting common workflows with dotfiles, for examples starting with my skeleton https://github.com/matu3ba/dotfiles_skeleton

Setup dotfiles to quickly restore broken configs. One simple options is https://github.com/matu3ba/dotfiles_skeleton

My position is that shells should be as simple as possible and any computations and tooling besides simple arithmetic be externalized: https://github.com/matu3ba/dotfiles_skeleton/blob/main/POSIXunsafe

I would recommend for you to start simple and incrementally improve or change plugins you dont like with dotfiles. My relative minimal dotfiles missing JavaScript lsp, debugger etc](https://github.com/matu3ba/dotfiles).

I dont believe there is "a best way", since requirements for dotfiles differ. For simple replications my [dotfile skeleton](https://github.com/matu3ba/dotfiles_skeleton) using fd with ignorefiles worked fine for me.

For easy managing your dotfiles on Linux (did not test Mac) you can usw my dotfiles skeleton.

Guess then you need to minimise the config to track down the issue. Do you use dotfiles? You could use my skeleton to easily branch and reset etc.

Create dotfiles or something different for versioning You can use my https://github.com/matu3ba/dotfiles_skeleton

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.