Shade.nvim VS which-key.nvim

I think this is done by rosstang/dimit.nvim, but might also be levouh/tint.nvim or sunjon/Shade.nvim.

hm, I don't get that behavior on my config. If you're using something like shade.nvim to dim your unfocused splits/windows that's probably setting the background to something besides NONE.

Why not using shade.nvim instead?

Are there plugins with proposals similar to Shade? I would like to know more, any recommendation?

The only thing I cna really add to the conversation is shade.nvim which is a cool concept, but I never really had a ton of luck with it. The difference between that and winhl is that it uses floating windows with alpha so even the foreground text looks properly dimmed.

Something like https://github.com/sunjon/Shade.nvim by default; so a way to handle window behaviours on focus/unfocus/enter/leave/etc. There are just so many edge cases that Shade.nvim is presently missing so it is broke for a ton of things.

Hey. I found it. https://github.com/sunjon/Shade.nvim This plugin was causing it.

Personally, I've had no issues with any emulator (Alacritty, Terminal.app, iTerm2, and previously st), but I also don't care about visual things in my editor. I don't use any icons and I use an unpatched font because, similar to you, I don't really want to go chasing dragons. I had to stop using the shade plugin even though I really liked it because it didn't work well with sessions, so I definitely don't give a lot of priority to visual elements.

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.