lsp-bridge VS omnisharp-vscode

You can try `lsp-bridge`, It's async so even if your language server is slow, the worst thing is that you won't see any completion candidate but can still keep typing: https://github.com/manateelazycat/lsp-bridge

you could also try lsp-bridge (https://github.com/manateelazycat/lsp-bridge), I have it on my todo list.

Unfortunately, because of your personal spam posts in Emacs China , you decided to fabricate such a lengthy article to slander me and my project? Below are some user feedback links for lsp-bridge, you can take a look: https://github.com/manateelazycat/lsp-bridge/issues/544 https://github.com/manateelazycat/lsp-bridge/pull/557 https://github.com/manateelazycat/lsp-bridge/issues/232 https://github.com/manateelazycat/lsp-bridge/issues/198 https://github.com/manateelazycat/lsp-bridge/issues/210 Here is my reply to you on Emacs China: https://emacs--china-org.translate.goog/t/lsp-bridge/24117/6?u=manateelazycat&\_x\_tr\_sl=auto&\_x\_tr\_tl=en&\_x\_tr\_hist=true I have been writing Emacs plugins for 18 years https://github.com/manateelazycat?tab=repositories&q=&type=source&language=emacs+lisp&sort= ， including the org-w3m.el has built-in in Emacs, and I have received countless thank-you emails. But your behavior, OP, which took malicious actions after being blocked due to a boring spam post in Emacs China, really shocked me.

So i have been trying out https://github.com/manateelazycat/lsp-bridge . the package is looking very good. But i couldn't figure out a way to run source.organizeImports code action using any of it's functions. If any of you guys have been trying it out or know already please help me out. My target is to bind a key to clean up unused imports.

They announced a year ago they are working on better C# support in VSCode https://github.com/omnisharp/omnisharp-vscode/issues/5276

OmniSharp (soporte de C# en VS Code): Licencia MIT

Let me try to find that post. It's basically the drama around this

> They did a wonderful job with C# and .NET Core.

And VSCode. One thing all three have in common is that they are all FREE to use--they don't make Microsoft any money directly.

And, for the segment of the developer tools market that wrangles C# code, if VSCode gets too good, it becomes a threat to a cash cow: Visual Studio.

Start here: https://github.com/OmniSharp/omnisharp-vscode/issues/5276#is...

Sounds like this issue https://github.com/OmniSharp/omnisharp-vscode/issues/2513

Open source. OP is referencing a decision Microsoft made last year to include some closed-source components, in particular the debugger from Visual Studio, in the default C# extension for Visual Studio Code. There is a Samsung-provided open source debugger available if you absolutely require it, but the closed source stuff doesn't have any usage restrictions afaik.