dap-buddy.nvim VS nvim-compe

There was also https://github.com/Pocco81/dap-buddy.nvim, but it's broken since some point and no longer maintained

Not a packer based solution, but you could also add something like this Makefile to set the runtime path at the plug-in's git root. This way you could just run make and test your plugin easily.

See https://github.com/Pocco81/dap-buddy.nvim/issues/71. The migration is uncomplete but the author didn't use a dev branch or something, so I'd recommend you pin at 24923c3 which is the latest version before the unexpected change.

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 )