kok.nvim VS nvim-compe

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

I use https://github.com/hrsh7th/nvim-compe and https://github.com/simrat39/rust-tools.nvim along with the built in LSP and auto completion works really well. You will want treesitter and all that setup too.

I want to share my code for my migration from nvim-compe (deprecated) to nvim-cmp. Though, I would describe myself as an experienced Vimmer I am not very familiar with the whole Lua thing (although I really appreciate it and hope that Lua's first class citizen can compete with the elisp ecosystem^^).

Wrong, plain and simple. A total misconception.

compe.nvim

For autocomplete/intellisense: https://github.com/hrsh7th/nvim-compe

But nvim-compe already exists.

completion-nvim OR nvim-compe

Here's some setup idea: - packer for package manager - clangd language server - nvim-lspconfig, required for navigator.lua - navigator.lua for enchanced IDE experience. This is a like adding a sugar to coffee. - completion-nvim OR nvim-compe for enchanching autocomplete & dropdown menu suggestion. - nvim-treesitter for better syntax highlighting. - telescope.nvim for amazing extensible & configurable fuzzy finder, you can also use fzf if you want. - Any custom color scheme you want (preferably one that supports tree sitter, like aurora )