dotfiles VS nvim-lsp-installer

Mostly shell hackery and a bunch of more convenient selection, copy and paste functionality plus extensive documentation like the (supposedly) undocumented line selection operator g_ https://github.com/matu3ba/dotfiles/

I am relative satisfied with mine, although I still dont have a working solution for (vendored) project search and custom sources on keypress for completion is also missing (command completion breaks C-l/Tab for file completion): https://github.com/matu3ba/dotfiles/tree/master/.config/nvim

My config consists mostly of documentation, where you can take a look. I have a plugin as git dir I do include for company stuff, because of network shenanigans packer can not handle. https://github.com/matu3ba/dotfiles

You can see my dotfiles here https://github.com/matu3ba/dotfiles/tree/master/.config/nvim

Otherwise, you can check my setup, but I did not setup snippets yet https://github.com/matu3ba/dotfiles

Thats how it works. You could reduce the amount of plugins or document them for quick lookup. I do this extensively in my dotfiles https://github.com/matu3ba/dotfiles/blob/master/.config/nvim/lua/my_packer.lua

For my config I did write a pile of notes of the default keybindings because I found no good and dense note collection on (all) default keybindings and Vim+Neovim hardcodes them with only an annoying way to search exact the exact keybinding. https://github.com/matu3ba/dotfiles/tree/master/.config/nvim

If you want a more minimal example for explanation, you can check my cmake template: https://github.com/matu3ba/dotfiles/blob/master/templates/CMakeList.txt

I find this cleaner to do in lua without vimscript calls, see here.

I had previous gotten a working setup with https://github.com/williamboman/nvim-lsp-installer however, I have been unable to get it working ever since.

The only way to stay up to date, is when you read the commits if you update the plugins. In this case for the lsp-installer in the commit bfa74f4 was mentioned that the plugin will no longer maintained

A word of caution, I believe lspinstall has been deprecated in favor of nvim-lspinstall which itself has also been deprecated in favor of mason-lspconfig

We have now migrated from nvim-lsp-instasller to mason which provides automatic LSP and null-ls configuration after installation

nvim-lsp-installer or mason.nvim. FYI lsp-zero also uses mason.nvim for managing installation.

I'm using nvim-lsp-installer it installs typescript when installing volar. So I had given it that path. Plus I had typescript locally installing since I'm using vue3+ts(vite) template

Though mason only recently replaced nvim-lsp-installer. Same author but they decided to make a complete rewrite given the broader scope beyond only providing language servers. And nvim-dap had it's initial release in late July. The actual dap servers are all kind of mature since they've been running on vscode for a couple of years or more now - and the protocol is apparently almost as old as lsp. So when I call them beta, it's more a commentary on the state of the neovim side of the ecosystem. If you mess around getting nvim-dap to work then there's a chance things might change over the coming months and you might have to return to configuring it more often than you'd like. In this sense for now I'm happy just to open vscode or another more appropriate IDE to debug. But I can see myself using the plugins in a year or two when they've matured.

Here are a few resources to get you started: 1. https://github.com/neovim/nvim-lspconfig 1. https://github.com/golang/tools/tree/master/gopls 1. https://github.com/williamboman/nvim-lsp-installer

Can recommend a combination of omnisharp-roslyn native LSP (installed manually or through something like mason or nvim-lsp-installer) with omnisharp-vim for some extra C#-niceties like OmniSharpRunTest, etc.