dotfiles VS which-key.nvim

My current setup has some issues, but you might find my dracula theme settings interesting. I added support for truecolor, darkened the background, and adjusted currentline color.

I keep them on github and my home directory contains a bare rpoe. I followed a guide to create my repo.

My dotfiles, which aren't super impressive.

This is what I do. I originally went the symlink route, but this is much easier to manage.

For more information: https://www.atlassian.com/git/tutorials/dotfiles and my dotfiles at https://github.com/mikeslattery/dotfiles

I maintain a dotfiles project in github (it also has /etc files in it). Helps when setting up another separate device.

I have a dotfiles project in github. In macos, I would just check it out into my home directory and have all my familiar settings like I have in Linux.

That's exactly what I created: https://github.com/mikeslattery/dotfiles

Create a dotfiles project, like mine

git clone --bare https://github.com/mikeslattery/dotfiles .dotfiles alias config="git -C $HOME --git-dir=$HOME/.dotfiles --work-tree=$HOME" config config --local status.showUntrackedFiles no config reset --hard

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.