deathaxe
deathaxe
But the older one looks way more complete and ST like, while the new one seems to be just a converted VS Code syntax.
If an unmaintained old package already exists with nearly the same (or less) functionality, a valid option was to replace it (or take over its name). Another but way simpler...
Should be fixed by PR https://github.com/sublimelsp/LSP-OmniSharp/pull/40, which makes transition to latest .NET 6+ based OmniSharp binaries. They are required to deal with latest .NET projects.
Should be fixed by PR https://github.com/sublimelsp/LSP-OmniSharp/pull/40, which makes transition to latest .NET 6+ based OmniSharp binaries.
Settings beginning with `"csharp"` are not supported by this package (removed by #43). Instead single language-server features can be disabled by `"disabled_capabilities"` dictionary in _LSP-OmniSharp.sublime-settings_. ``` { "disabled_capabilities": { "codeLensProvider":...
Should be fixed by PR #40, which makes transition to latest .NET 6+ based OmniSharp binaries.
This should be possible by adding `"command"` setting to _LSP-OmniSharp.sublime-settings_ ```json { "command": [ "OmniSharp", "--languageserver", "--encoding", "utf-8" ], } ```
Obsolete issue as of PR #40.
Should be fixed by PR #40, which makes transition to latest .NET 6+ based OmniSharp binaries. They are required to deal with latest .NET projects.
How is this request related with OmniSharp language server?