csharp-language-server VS vim-polyglot

The recommended approach used to be coc-omnisharp, but it has been discontinued in favor of chsarp-ls. I have installed csharp-ls with dotnet tool install --global csharp-ls, and the executable is on ~/.dotnet/tools. The following is on my coc settings:

I switched to https://github.com/razzmatazz/csharp-language-server which doesn't have as many features.

Apropos lsp, these two might be interesting, if you haven't yet given up on C#. Again, that should work on many editors, including the evil one at hand. Note how both explicitly name vim, emacs and vscode in their documentation.

It using lsp protol.i tried the new version of omnisharp with lsp but its really bad, 2 client extension if you don't want to use omnisharp https://github.com/statiolake/vscode-csharp-ls And https://github.com/vytautassurvila/vscode-csharp-ls And last, server lsp https://github.com/razzmatazz/csharp-language-server

lol quite specific. do you know https://github.com/razzmatazz/csharp-language-server ?

There's Saulius's lsp too too, altogh I haven't tried it yet.

You could also set the semantic tokens capability to nil. Another alternative to omnisharp is csharp-language-server which has recently added support for semantic tokens.

I ended up using csharp_ls, https://github.com/razzmatazz/csharp-language-server/issues/34 posted what I found here. Once I got things pointing to the right mono dll it started working great.

Sadly, OmniSharp (the LSP for vscode and nvim) isn't all that great. The performance is incredibly bad, easily orders of magnitude worse than VS and Rider.

There is this alternative LSP, which I plan to try out still: https://github.com/razzmatazz/csharp-language-server

I don't know about your case, but wanted to add a comment. I had some problems recently with omnisharp, and someone recommended me to try https://github.com/razzmatazz/csharp-language-server instead of omnisharp, I switched and so far with no issues.

I'm currently on an old setup (using coc and polyglot) and nvim v0.6.1. I'll be updating to a more modern setup within next year, using the native lsp and building nvim more frequently. But that's not today.

So I did some digging and I found out that vim-polyglot uses a different syntax file than Vim's default for PHP files. When I loaded vim-polyglot's syntax file into my ~/.vim/syntax, I encountered the same issue as you.

Try this: https://github.com/sheerun/vim-polyglot You can install plugin or copy-paste files for desired filetype

I think you mean vim-polyglot? Great plugin. Pre-treesitter it was indespensible.

Usually this is handled inside the :compiler scripts. vim-polyglot is a collection of ftplugins that includes a bunch of :compiler plugins.

Get polyglot installed in your vimfiles/pack//start folder along with whatever 4 Tim Pope plugins you love the most and :CocInstall your LSP(s)

https://github.com/morhetz/gruvbox and https://github.com/sheerun/vim-polyglot are Vim plugins that work in Neovim, but they don't allow you to use treesitter, so if you don't want to use treesitter use them.