dotfiles_skeleton VS nvim-lsp-installer

You can also use my dotfiles skeleton to see, if you have different demands. https://github.com/matu3ba/dotfiles_skeleton

Personally it would have helped me to start outright with version tracking and documenting common workflows with dotfiles, for examples starting with my skeleton https://github.com/matu3ba/dotfiles_skeleton

Setup dotfiles to quickly restore broken configs. One simple options is https://github.com/matu3ba/dotfiles_skeleton

My position is that shells should be as simple as possible and any computations and tooling besides simple arithmetic be externalized: https://github.com/matu3ba/dotfiles_skeleton/blob/main/POSIXunsafe

I would recommend for you to start simple and incrementally improve or change plugins you dont like with dotfiles. My relative minimal dotfiles missing JavaScript lsp, debugger etc](https://github.com/matu3ba/dotfiles).

I dont believe there is "a best way", since requirements for dotfiles differ. For simple replications my [dotfile skeleton](https://github.com/matu3ba/dotfiles_skeleton) using fd with ignorefiles worked fine for me.

For easy managing your dotfiles on Linux (did not test Mac) you can usw my dotfiles skeleton.

Guess then you need to minimise the config to track down the issue. Do you use dotfiles? You could use my skeleton to easily branch and reset etc.

Create dotfiles or something different for versioning You can use my https://github.com/matu3ba/dotfiles_skeleton

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.