coc-fzf VS nvim-compe

I use coc.nvim and fzf. You can find a screenshot at https://github.com/antoinemadec/coc-fzf

Interesing, multiple people mentioning nvim-bqf, which I use, but for Coc I have been using https://github.com/antoinemadec/coc-fzf for a long long time.

And as normal plugins my workflow is very fzf-centric. I have installed fzf.vim and https://github.com/antoinemadec/coc-fzf.

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 )