Open nicolaiarocci opened 1 year ago
I suspect omnisharp-vim is a red herring here. If you are using neovim LSP, then neovim and omnisharp are each starting their own versions of the omnisharp-roslyn server - one in lsp mode and one in the older stdio mode. The omnisharp-vim log can be seen with :OmniSharpOpenLog
.
@nickspoons thanks for the feedback. :OmniSharpOpenLog
shows that the omnisharp-roslyn server is running in stdio mode. As mentioned I get the weird editorconfig behavior even if omnisharp-vim is disabled (same errors in the log).
I got neovim working just fine with omnisharp-roslyn and the companion omnisharp-vim plugin; code refactorings & analysis function as expected.
Howewer, if I add a
.editorconfig
file to the project, while the rules are respected in code analysis, all code refactorings fail silently. A look at the logs shows thatNotSupportedException
exceptions are raised:The same happens with the omnisharp-vim plugin disabled. Removing the
.editorconfig
file (and relaunching the editor) will reactivate refactorings.EDIT: I should probably mention that I am also suffering from #2483 (and have the suggested workaround in place).