-
Notifications
You must be signed in to change notification settings - Fork 168
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
:OmniSharpBuild not working with Roslyn server #345
Comments
Yes, there are some features that have never been set up properly with the roslyn server unfortunately - either because roslyn doesn't support them, or roslyn just has different request/response structure and needs tweaking on the OmniSharp-vim side. So I think some of the documented commands and functionality really need to be removed from the documentation - hopefully temporarily, and then we can add them back in again once someone gets them working. |
In the meantime, you can build using vim and
I have done this before on arch but I can't exactly remember what was required. I think there's a mono-based |
I haven't used |
Thanks for the vim magic. Though I had to hardcode my sln file's location, and for some reason the quickfix filename gets messed up when I build asynchronously. It's working well enough now though. |
If the quickfix filenames are bad it's probably the |
It's correct when I use
I thought it might be related to color, but I passed "/consoleloggerparameters:DisableConsoleColor" to msbuild and that didn't fix it, so I'm not sure. |
Closing this in favour of #386 |
Currently trying to transition to Roslyn, which hasn't played nice with me in the past. Running Arch Linux.
When I run the command "OmniSharpBuild", vim errors out with this output:
The "FixIssue" command gives a similar error. However, autocompletion and warnings are working properly.
I installed the roslyn server "omnisharp.http-linux-x64.tar.gz v1.29.1". I wasn't sure whether to use this or the "mono" variant, but they both seem to give the same problem.
Vim version information:
The text was updated successfully, but these errors were encountered: