niscolas

I actually was able to maintain a sustainable workflow by creating a second class (let's say `Foo.cs`) on a already "Synced File" (where the LSP features work normally) and using...

I'll test that approach later. But what I've found is it seems like there're 2 different problems. There're some repos on GitHub mimicking the behavior of Unity plugins for VSCode...

That's great to hear! Is this change on the repo yet?

Following the idea from @nickspoons above (with my little knowledge of LSPs) I tried to find if there's a way to make a similar request to this `/filesChanged` in to...

@0rphee I think that for being able to work without major issues with Unity (except the one discussed in this issue), you need: - A properly working Neovim + LSP...

@nyngwang > @niscolas I finally found something related: [neovim/neovim#21293](https://github.com/neovim/neovim/pull/21293), which is a PR that could be an important factor in finding/creating the solution to the problem. That's super interesting! That...

Yay, that's great! I'll be taking a look as soon as I can to check whether it solves the issue and if we will still need some kind of plugin...

I believe that I just got it to work. - You should be using a build for Neovim that includes the changes in the PR above ([link](https://github.com/neovim/neovim/pull/21293)), I recommend just...

I only tested this by creating the file through Unity, so I think it automatically adds the file to the `Assembly-CSharp.csproj`. If creating files directly from Neovim, there's the need...

Maybe adding an option for the format in the `optimus-manager.conf` would help in this case