kok.nvim VS which-key.nvim

In the examples listed on this page https://github.com/ms-jpq/coq_nvim, there is a pattern overlay over the whole screen. Is there a neovim plugin that does this? Thanks.

nvim-cmp or coq_nvim is for autocompletion. Treesitter is for parsing language syntax. (I guess the most typical use case for this would be syntax highlighting.) Note that (neo)vim also has built in manual completion that you can use by setting up your omnifunc and triggering it with in insert mode .

Aw man that's not nice to hear. I have had my own struggle with lsp not gonna lie. I used to use coc until it got too slow, after struggling for like 2 days lol lsp is working fast and neat. I'd suggest you to take a look at coq https://github.com/ms-jpq/coq_nvim which claims to be fast as fuck (literally lol) and also claims to be faster than lsp (because its written using c or something). Haven't tried it personally

Coq_nvim

I'm attempting to use (coq_nvim)[https://github.com/ms-jpq/coq_nvim]. This is my config:

Does your coq_nvim and nvim-lspconfig really load? Because they have opts = true

I'd be happy for someone who knows more about this to correct me. But in my experience as well, nvim-cmp is not as good completion as vscode, its suggestions can be all over the place sometimes. I found that coq_nvim tends to better in this regard. I still prefer nvim-cmp for other reasons but you should definitely try coq_nvim out and see if you have a better experience.

Coq_nvim isn't the same as Coc.nvim. Coq is a completion plugin with lots of caching written in Python that works alongside the builtin LSP. Coc is an LSP client (and has it's own plugin ecosystem) written in Node.

There are some like https://github.com/SirVer/ultisnips and https://github.com/ms-jpq/coq_nvim. Speed is not really an issue, I guess people just prefer to have fewer dependencies and use lua which is already bundled in neovim.

Maybe using coq.nvim instead of nvim-cmp could help (?) dince it caches the LSP responses. I haven't test it, though

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.