-
Notifications
You must be signed in to change notification settings - Fork 420
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't get it working in Vim, but my VSCode works #1811
Comments
related #1777 |
This seems like the wrong place to ask - you are asking lots of different questions with no details necessary to answer them. OmniSharp-roslyn has several different modes it can run in, the relevant ones being VSCode and OmniSharp-vim use the stdio mode. I can help you with OmniSharp-vim, if you open an issue over there. Please include your environment details, and an OmniSharp-roslyn log will be helpful (in Vim, get this with |
Thank for the reply. As I was not sure which path to take, it didn't feel useful to provide a dump of all the info I gathered first. I am looking for pointers that would help me provide the relevant info. The LSP vs stdio is what I was looking for. That helps. I will file an issue with you with the relevant logs/etc. Appreciate it. Thanks! |
Hey all,
Thank you for the time you spend on this project! Really appreciate it.
I've been having a really hard time getting a reliable C# dev experience working with NeoVim. I am focusing on Unity3D at the moment. I've tried many approaches:
I fire up VSCode as a comparison, and that works. Not super reliable, but certainly works where NeoVim doesn't. I even pointed NeoVim plugins at the same omnisharp.exe that VSCode uses, nope... doesn't work.
What wizardry is VSCode doing? Based on my understanding of LSP as a protocol, it shouldn't matter. VSCode is just a client same as CoC, etc.
Any ideas on how I can figure this out?
The text was updated successfully, but these errors were encountered: