omnisharp-roslyn VS distant.nvim

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

Oops, meant distant, https://distant.dev/.

2) There is a remote working plugin to not have the overhead of sshfs copying around files https://github.com/chipsenkbeil/distant.nvim, but you could also role your own with neovim now having remote mode and lua runner. Main caveat is how to get consistent file system view.

- What do you think of other plugins e.g.: https://github.com/chipsenkbeil/distant.nvim?

This is something I've been tracking pretty closely. My understanding of the current options: 1. Use sshfs. Pros: nothing to install on the remote server. Cons: will choke on huge filesystems when doing some operations (e.g. fuzzy finding). Also requires all your LSP/linting/analysis tools to be installed locally, which may not be the case if your company is transitioning to remote developer environments. 2. Use netrw or similar. Pros: nothing to install. Cons: will not play nice with LSP, fuzzy finding, or anything else. 3. Use distant.nvim. At this point, basically the same as netrw except that maybe remote LSP will work. 4. SSH to the server and use nvim there. Pros: simple and everything works. Cons: Have to install nvim on the server. SSH connection may cause typing lag if the RTT is high (some people report that Mosh can help the lag issue)

The reason being is that I've written a service called distant with a companion neovim plugin, distant.nvim, and want to provide forms of authentication in the same vein as ssh.

Did a lot if research. there is distant.nvim that tries to solve it maybe it will work for you.

I either use the vi / vim that's on the server or connect remotely using https://github.com/chipsenkbeil/distant.nvim

Regarding the last part of your comment: you may get some value out of this plugin, https://github.com/chipsenkbeil/distant.nvim, https://www.youtube.com/watch?v=wVAsbpByQ3o.

I've not used it but your use case made me wonder if there's a nice way to do it, as I regularly SSH into my NAS and RPi's, so I had a quick search.