tabby.nvim VS which-key.nvim

I use nanozuki/tabby.nvim (the original tabby!) for a beautiful, highly functional tabline and tiagovla/scope.nvim to limit buffers to tab scope.

What are the differences between tabby.nvim

I use tabby.nvim to switch amongst the active tab pages.

- The Tabby plugin, which offers a tabline. However the buffer list dependent of each tab is a feature request but without any accessible solution for a novice like me.

The owner seems to let this implementation as an exercise to the user according to this issue

Support restoring "TabName" of nanozuki/tabby.nvim Resolves issue #75 by a lightweight external dependency. So now you have persistent "TabName" for each project :)

tabline (not enough respect for tabs imo) https://github.com/nanozuki/tabby.nvim

tabby.nvim by default only lists the buffers in the windows on the tabpage

nanozuki/tabby.nvim (github.com)

I'm using tabby.nvim. I uploaded my tabby-config to https://pastebin.com/jxRq7Knz if you're curious.

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.