search

OmniSharp / omnisharp-vim

Vim omnicompletion (intellisense) and more for C#
http://www.omnisharp.net
MIT License
1.72k stars 168 forks source link

Autocomplete excludes documentation #630

Closed BrandtWright closed 4 years ago

BrandtWright commented 4 years ago

I recently decided to give omnisharp-vim a try and I can't get intellisense/autocomplete to show documentation. I am running an up-to-date version of Arch linux, vim, the latest version of dotnet core, and the latest version of vim, omnisharp-roslyn-stdio-bin.

dotnet --version: dotnet-version.txt

dotnet --list-sdks sdk-versions.txt

:OmniSharpDocumentation OmniSharpDocumentation

:OmniSharpSignatureHelp OmniSharpSignatureHelp

I have spent some time digging around other issues and googling but everything I find suggests that older versions of dotnet core on arch requires some work arounds to get things working correctly (DOTNET_ROOT, symlink the script to /opt/dotnet, etc) but it looks like these are no longer needed and I am at a bit of a loss as to why I can not get this to work right. Current docs suggest this should all work out of the box but that isn't what I am finding. Any suggestions would be greatly appreciated.

BrandtWright commented 4 years ago

Turns out this was due to a configuration issue on my end and not a problem with omnisharp-vim.

godskiy commented 4 years ago

Turns out this was due to a configuration issue on my end and not a problem with omnisharp-vim.

So what did you do to fix it? Looks like I have kinda same problem, but can't figure out

nickspoons commented 4 years ago

This is what @BrandtWright wrote in Slack about this issue, if it helps:

hmmmm. This is interesting. I was testing omnishap-vim with a class library (dotnet new classlib). No documentation in popups. I changed TargetFramework from netstandard2.0 to netcoreapp3.1 in the csproj file and viola.... popups now contain documentation... Any idea why that could be?

Ahhh.... Needed netstandard2.1. That makes sense. Banging my head against the wall for nothing and assuming it's a bug with the plugin. The problem was that I don't understand the APIs. I am more of a Java/Haskell/Python guy and figured I would give dotnet core a go. There are certainly a lot of nuance in that world. Sorry for the confusion folks.

Just figured the "dotnet new" tooling would generate the framework references that made sense (as I have only installed dotnet core 3.1 with no other frameworks living next to it). Guess that isn't the case.