nest.nvim VS kok.nvim

However, I will shamelessly plug my plugin nest.nvim which I wrote to have a nice API to manage keymaps in Lua :-)

(shamelessplug) nest.nvim supports binding lua functions directly while also cleaning up your kenind code ;-) (/shamelessplug)

I will shamelessly plug my plugin nest.nvim here - it is a small lua utility to set your keybinds in lua config in a nice syntax. It also supports binding lua functions.

A few other plugins exist that provide similar functionality, like nest.nvim and nvim-cartographer, but what differentiates Mapx is that my goal was to build upon and improve Vim's familiar style of creating mappings that many of us are used to.

I just released version 1.1 of nest.nvim, adding several new core features:

(shameless plug) May I recommend nest.nvim to manage your keybinds in Lua? :-) (/shameless plug)

nest.nvim ;-P

While that cannot work for "normal" bindings when you pass `expr`, I could actually handle that special case (`expr` + `lua` rhs) within nest.nvim pretty easily 🤔

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