coc-explorer VS nvim-compe

I use coc-explorer for a long time already since I use `coc.nvim` also. Lots of features/configurations, handy shortcuts, and quite performant.

For vim, I am not aware of a way to do with NERDtree, only aware of using https://github.com/weirongxu/coc-explorer/ with https://github.com/neoclide/coc.nvim

I like coc-explorer, but I really hardly use a file tree so I can't say if it has any weird behaviour. Fzf is usually enough for me.

might give coc-explorer a try if you haven't ;)

However, if you are using plugins, something like coc-explorer works little better, and you can do little more with that (ex. copy/move/delete files).

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 )