Closed EliSauder closed 1 year ago
I'm having this issue as well when using omnisharp-mono
after reinstalling NeoVim due to an unrelated issue. This could be related to omnisharp-roslyn/#2483. What's strange is that this was working about a month ago when I first installed omnisharp-mono
, but after reinstalling I'm getting this issue.
Semantic highlighting was somewhat recently added to neovim. Try
To opt-out of semantic highlighting with a
server that supports it, you can delete the semanticTokensProvider table
from the {server_capabilities} of your client in your |LspAttach| callback
or your configuration's on_attach
callback:
client.server_capabilities.semanticTokensProvider = nil
Semantic highlighting was somewhat recently added to neovim. Try
To opt-out of semantic highlighting with a server that supports it, you can delete the semanticTokensProvider table from the {server_capabilities} of your client in your |LspAttach| callback or your configuration's
on_attach
callback:client.server_capabilities.semanticTokensProvider = nil
Thanks! That stopped the spam of E5248 errors.
Problem description
After installing the omnisharp from the :Mason page, I will get E5248: Invalid character in group name whenever I open a .cs file.
Why do you think this is an issue with mason-lspconfig.nvim?
The issue only shows up when I have installed omnisharp from Mason, I have also tried the omnisharp-vim plugin and I haven't gotten dhe same issue.
Also I see several of this in the LspLog:
Neovim version (>= 0.7)
NVIM v0.9.0 Build Type: Release LuaJIT 2.1.0-beta3
Operating system/version
Darwin Kernel Version 22.4.0: Mon Mar 6 20:59:28 PST 2023; root:xnu-8796.101.5~3/RELEASE_ARM64_T6000
I've manually reviewed the Nvim LPS client log (
:LspLog
) to find potential errorsI've recently downloaded the latest plugin version of mason.nvim, mason-lspconfig.nvim, and nvim-lspconfig
Affected language servers
omnisharp
Steps to reproduce
Actual behavior
The LSP appears to work, but the E5248 error keeps poping up whenever I move around in the file.
Expected behavior
The E5248 should not show up and it should work normally.
LspInfo
LspLog
Healthcheck
Screenshots or recordings