lush.nvim VS which-key.nvim

I've been spending the last couple days creating a custom colorscheme with lush.nvim that covers as many highlight groups as possible to support all the plugins I use.

appreciate ya buddy ✌️ just discovered lush today, so expect a lot more color scheme action from me in the near future

Add this as a dependency to tree climber: https://github.com/rktjmp/lush.nvim

Hi, I have just created my first color scheme using lush.nvim. I named it "basic".

OP, have you heard of lush.nvim?

A fancy but yet sophisticated light and dark designer neovim theme built in pure lua with lush.nvim. It features a comprehensive usage of syntax scopes and color consistency, with due regards to aesthetics, contrast and readability.

Thought I'd plug lush here which has a really nice way of doing this automatically.

Lush users should see issue 109 for migration details/workaround. May change (improve?) in the future.

Lush looks interesting. Live prevew https://github.com/rktjmp/lush.nvim

lush.nvim: Cusizme and compile color theme.

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.