LuaSnip VS nvim-lsp-installer

If you're using Neovim, check out LuaSnip: https://github.com/L3MON4D3/LuaSnip

I’ve been using LuaSnip and never put much thought into it. And this was mainly because of because it seemed like the default and had good LSP integration. The one downside is that creating custom snippets is not that ergonomic, but I don’t mind it if it’s the price to pay for speed.

You can use LuaSnip and load snippets from VSCode. The documentation is pretty complete, but here is my config in case you want another reference.

I am trying to add snippets for python, i have LuaSnip and friendly-snippets installed, but for some reason it does not load the snippets. This is how i load the plugins:

There was a similar issue in LuaSnip repo. The culprit was a keymap in the config. Do you happen to have a similar keymap somewhere in your config?

I have decided to extract my Haskell snippets for LuaSnip into a plugin: haskell-snippets.nvim.

Not exactly what you're talking about but you could look into LuaSnip?

There are a few more resources for new users as well on the official repo, and you can find the implementation in Examples/snippets.lua

You mean snippets? If yes, you can try Luasnip and friendly-snippets with nvim-cmp and here's the setup guide. Hope it helps

I had the same issue recently. It was the case when I inserted a snippet but didn't fill out all the placeholders right away. This helped me. This is an autocommand that unlinks the unfinished snippet when you change the mode.

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.