Closed scizo closed 8 years ago
Hi @scizo! Which version of fsautocomplete is bundled with vim-fsharp these days? fsautocomplete --version
should tell you.
Hi @rneatherway,
Currently we bundle version 0.23.0
https://github.com/fsharp/vim-fsharp/blob/master/Makefile#L11
Thanks, so Android should be supported, although I haven't tested it myself. @scizo, bearing in mind that I haven't used Mono.Android myself, what is the easiest way to reproduce? Do I need to install anything other than the standard Xamarin Mono installation, perhaps plus Xamarin Studio?
@rneatherway I am not sure if there is a more minimal way to reproduce it, but I installed all of the mono components through the Xamarin Studio installer (https://xamarin.com/download). Although I did avoid the registration by using homebrew on mac. After it was downloaded I used Xamarin Studio to generate the standard Android application as follows. File > New > Solution. I then selected the Android App option with the language set to F#.
The next screen had three optional target platforms. I selected the top one, Modern Development, but I don't believe that would make a difference, but just in case.
After the project was created, open the MainActivity.fs file in vim should demonstrate the problem.
If that is too much, I can try and generate a standalone reproduction of the problem, but I hope that makes it possible for you to reproduce.
Thanks!
Can you explain a bit about what you mean when you say you skipped registration using Homebrew? Also, just to check, does autocomplete work in Xamarin Studio for this project?
When I say that I skipped registration using Homebrew I mean I was able to download the installer with out filling in the registration form on the download page by running brew cask install xamarin-studio
from the command line. Once Xamarin Studio was installed though, I did register for an account so that I was able to browse the Xamarin Component Store though.
Autocomplete does work from Xamarin Studio for the project.
I don't know if I should mention my problem here or open a new issue. It seems that in a minimal project (created either in Visual Studio or in Projekt) some of the modules in System
are not found by fsautocomplete (I tried System.Diagnostics.Process
), and error messages are emitted in Vim with vim-fsharp. MSBuild and fsc, on the other hand, compile it just fine. I have reported this issue in fsautocomplete: https://github.com/fsharp/FsAutoComplete/issues/72.
@scizo: I'm sorry, I haven't had time to test this. If you have time, the easiest way to find out what the problem is as follows:
let p = FSharpProjectFileInfo.Parse(file, enableLogging=true)
and add printfn "%s" p.LogOutput
on the next line.fsautocomplete.exe
from the project directory, and then type `project "Let me know what the output is.
fsac issue 72 referenced above has been closed. @yever do you need me to keep this issue open?
@kjnilsson, sorry for my disappearance.
This issue can be closed, as far as I'm concerned. I've just tested a project created in monodevelop and finally got autocompletion for System.Diagnostics.Process
. If there still is a problem with project files created by Visual Studio, it should be treated in a separate issue.
ok thanks - no worries. :)
This issue might actually not be a vim-fsharp problem, but be better addressed to the FSAutocomplete project (I'm not sure if I am refering to the project correctly).
Anyways, here is what I am experiencing.
I have a .fsproj file generated by Xamarin Studio. When I open one of the files in my project (a Xamarin Android project) it doesn't have references to the Mono.Android assemblies and thus marks all of the lines referencing classes from these assemblies as errors. When I turn on debugging, and look at the logs, the Mono.Android assemblies are not included in the references section although they are in the .fsproj file. I will include the contents of my *.fsproj and the log2.txt debugging output.
Is there something else that I need to do in order for the Mono.Android assembly to correctly be referenced or is this a bug when parsing the *.fsproj file?
Thanks for a great plugin! The intergration with fsi and everything else has been fantastic besides this little hiccup.