dotfiles VS omnisharp-roslyn

code

I code in C#. The biggest issue you are likely to have is the debugger, everything else is straightforward. You'll need netcoredbg from samsung to use with nvim-dap. You can view my dotfiles here: https://github.com/cseickel/dotfiles

Here's my personal winbar and statusline setup: https://github.com/cseickel/dotfiles/blob/main/config/nvim/lua/status.lua

Sure: https://github.com/cseickel/dotfiles/tree/main/config/nvim

I'm sharing this for others that are looking for examples on how to do this in their PDE (Personalized Development Environment). Feel free to just take it and customize it to your liking, most of the stuff you are likely to change is at the top of the file: https://github.com/cseickel/dotfiles/blob/main/config/nvim/lua/status.lua

and I start it with this script: https://github.com/cseickel/dotfiles/blob/main/start-arch-linux-docker.sh

If it helps, I work out of this Dockerfile: https://github.com/cseickel/dotfiles/blob/main/Dockerfile

I do have some overrides to the colors in my config: https://github.com/cseickel/dotfiles/blob/main/config/nvim/plugin-config.vim

I have no issue using omnisharp via the built-in LSP. I would look at your config and check for errors in the omnisharp logs. My dotfiles are messy, but this is a functional config: https://github.com/cseickel/dotfiles/tree/main/config/nvim

They are not all that tidy, but you can view my dotfiles here: https://github.com/cseickel/dotfiles

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.

I've been using Neovim (on Windows, not WSL) with Unity and the Omnisharp LSP smoothly for a while now, and it's definitely possible to have a decent experience. Assuming your config is already setup for LSP, completion, snippets, etc., there are a few Unity/Omnisharp specific workarounds to be aware of:

I solved it using the workaround at the end of this issue thread in omnisharp-roslyn

See: https://github.com/OmniSharp/omnisharp-roslyn/issues/2483 for some solutions.

No, Sematic Tokens has an issue opened for it since Dec 2022, with couple (well, at least one that I have seen) PRs open trying to fix it and some hacking around the issue in the comments, but it's not solved afaik.

Have a Look at this

I think the issue is related to 'Semantic Tokens' introduced in version 0.9 https://github.com/OmniSharp/omnisharp-roslyn/issues/2483

I did, but it's a little bit tricky. If you could wait some hours I will share it with you after work. You can take a look at this thread first: https://github.com/OmniSharp/omnisharp-roslyn/issues/2250