Markus Törnqvist

This is going to proceed sporadically and I may be dumping notes here more than what's professional, but I did upgrade OmniSharp for test's sake, v1.39.11, and it actually works...

Not sure it's the space character. What lead me down that path was that there was a weird stderr notification in omnisharp's log, with some garble, so I thought maybe...

I went down another rabbit hole. The 2020 version (Assembly-CSharp.proj) has TargetFrameworkVersion v4.7.1 which is completely missing in the 2021 version. The 2020 version has (grabbed from this post https://stackoverflow.com/questions/66570036/how-to-change-target-net-framework-used-in-unity-2019)...

Something like https://spaceandtim.es/code/nvim_unity_setup/ makes things seem so easy, but even with on-demand loading the best I can get with Unity 2021.3 is a very slow startup for autocompletion and never...

This https://forum.unity.com/threads/unity-future-net-development-status.1092205/ must be very related. Apparently C# 8 is supported but not .NET 8, and OmniSharp is out of sync with their fork of mono or something. https://forum.unity.com/threads/net-5-support.839890/page-6#post-7029694 should...

I'm also busy with other things, but I did dig this old setup out of the mothballs. It's nvim 0.7.2, OmniSharp 1.38.0, and using mono (ie. the bundled mono, it...

I did quickly dig out this https://github.com/neovim/nvim-lspconfig/blob/master/lua/lspconfig/server_configurations/csharp_ls.lua which may be important, as deoplete-lsp doesn't seem to "do" much. Sadly deoplete is considered dead, and Shougo's replacement ddc requires (apparently) a...