deoplete.nvim VS nvim-lsp-installer

I think in-the-wild examples like Ultisnips deoplete semshi (although they are advanced and somewhat complex) would also be good examples to learn how one can use python for writing plugins.

If you post your issue on https://github.com/Shougo/deoplete.nvim/issues, Shougo might be able to better assist you.

I have a problem with Deoplete and Vim-LSP completion (Python's Pylsp and Jedi-Language-Server). The suggestion is much less, and it also misses a lot of opportunities to suggest compared to Deoplete-Jedi, which literally defeats the former by a large margin. Is there a setting to make this duo works like deoplete with deoplete-jedi?

Someone made an issue on this question, with the author suggesting float-previewnvim.

This exactly why I keep using deoplete! Other completion plugins don't handle middle of word completion correctly.

As we can see, it's a deoplete issue. By reading the docs at https://github.com/Shougo/deoplete.nvim, under the requirements section, it needs nvim to be compiled with python support.

Hmm. Maybe I don't know what to look for (not an expert at vim), but I have searched the deoplete documentation and I can't see any options to allow as-you-type omnicompletion. There are things like external sources, but I don't need that. Everything is available from , I just need that to be automatic.

For me I've been using deoplete.nvim for everyday use and for a long time and will probably transition to [ddc.vim](https://github.com/Shougo/ddc.vim] which is the next iteration after deoplete from the same author and is very similar to cmp in terms of setup with user customization.

To my knowledge thats not possible with omnicompletion. For this you would have to use an auto-completion plugin. I am using compe because its fast, minimal and integrates well with the builtin nvim-lsp but there are many others. The most popular is probably coc. You could also check out deoplete.

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.