Installation issue, nothing happens when using <leader>t or similar

[mschlaipfer]

I've followed the steps to install vim-fsharp via Pathogen on Linux, but nothing happens when I use \<leader>t or similar. Syntax highlighting works, however. I've also tried to run install.sh, but no difference. Is there anything else I need to do to run the autocompletion server? I can run the binary in ftplugin/bin with mono.

[kjnilsson]

Have you got syntastic installed? On Sun, 8 Jan 2017 at 13:07, Matthias Schlaipfer notifications@github.com wrote:

I've followed the steps to install vim-fsharp via Pathogen on Linux, but nothing happens when I use t or similar. Syntax highlighting works, however. I've also tried to run install.sh, but no difference. Is there anything else I need to do to run the autocompletion server? I can run the binary in ftplugin/bin with mono.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/fsharp/vim-fsharp/issues/65, or mute the thread https://github.com/notifications/unsubscribe-auth/ABIDlKr4Nb7m7xrh5dZ-KZVCch-Bcroeks5rQN-MgaJpZM4Ldr01 .

[mschlaipfer]

Yes, output of SyntasticInfo is:

Syntastic version: 3.8.0-14 (Vim 704, Linux, GUI) Info for filetype: fsharp Global mode: active Filetype fsharp is active The current file will be checked automatically Available checker: syntax Currently enabled checker: syntax

[kjnilsson]

Python 2 support in vim?

[mschlaipfer]

echo has('python') is 1

[kjnilsson]

How did you install vim? On Sun, 8 Jan 2017 at 13:14, Matthias Schlaipfer notifications@github.com wrote:

echo has('python') is 1

— You are receiving this because you commented.

Reply to this email directly, view it on GitHub https://github.com/fsharp/vim-fsharp/issues/65#issuecomment-271150459, or mute the thread https://github.com/notifications/unsubscribe-auth/ABIDlEKIwb8BiAsu2pr4Wwou2JrBtKaqks5rQOFIgaJpZM4Ldr01 .

[mschlaipfer]

Nothing crazy AFAIR, using apt-get in Debian testing. Edit: Ah, you might be onto something here. I'll see if my vim has python2 support.

[kjnilsson]

Not sure what else to suggest. Try vim8 or record a screencapture of you testing the plugin. On Sun, 8 Jan 2017 at 13:21, Matthias Schlaipfer notifications@github.com wrote:

Nothing crazy AFAIR, using apt-get in Debian testing.

— You are receiving this because you commented.

Reply to this email directly, view it on GitHub https://github.com/fsharp/vim-fsharp/issues/65#issuecomment-271150781, or mute the thread https://github.com/notifications/unsubscribe-auth/ABIDlAkbNTD0AZ_J5HGX06N3UhzoUrSsks5rQOK-gaJpZM4Ldr01 .

[mschlaipfer]

Hm, so :python import sys; print(sys.version) outputs

2.7.11+ (default, Feb 22 2016, 16:38:42) [GCC 5.3.1 20160220]

I think I have Python 2 support in Vim7.4, only Vim8 seems to have changed to Python3.

Okay thanks, I've recorded my screen: https://www.dropbox.com/s/usnyxkwatf9pcxs/Screencast%202017-01-08%2014%3A46%3A06.mp4?dl=0

My leader is ",", so I try to get type of the variables at some point of the capture. Also Syntastic doesn't complain about assigning from an undefined variable. Let me know if you'd like to see something else.

Thanks for taking your time!

[kjnilsson]

Delete fsharpbinding-vim On Sun, 8 Jan 2017 at 13:51, Matthias Schlaipfer notifications@github.com wrote:

Hm, so :python import sys; print(sys.version) outputs

2.7.11+ (default, Feb 22 2016, 16:38:42) [GCC 5.3.1 20160220]

I think I have Python 2 support in Vim7.4, only Vim8 seems to have changed to Python3.

Okay thanks, I've recorded my screen: https://www.dropbox.com/s/usnyxkwatf9pcxs/Screencast%202017-01-08%2014%3A46%3A06.mp4?dl=0

My leader is ",", so I try to get type of the variables at some point of the capture. Also Syntastic doesn't complain about assigning from an undefined variable. Let me know if you'd like to see something else.

Thanks for taking your time!

— You are receiving this because you commented.

Reply to this email directly, view it on GitHub https://github.com/fsharp/vim-fsharp/issues/65#issuecomment-271152399, or mute the thread https://github.com/notifications/unsubscribe-auth/ABIDlODMjHmC7kj9CNXIvKxa1vE6zhD1ks5rQOnSgaJpZM4Ldr01 .

[mschlaipfer]

I have tried both before and after install.sh (i.e. with fsharpbinding-vim not present). It doesn't make a difference unfortunately.

[kjnilsson]

Ok it defo wont work with fsharpbinding-vim around. I should mention that in the readme. Can you remove fsharpbinding-vim, git clean -dfx the vim-fsharp repo and run make (not install.sh)?

On Sun, 8 Jan 2017 at 14:21, Matthias Schlaipfer notifications@github.com wrote:

I have tried both before and after install.sh (i.e. with fsharpbinding-vim not present). It doesn't make a difference unfortunately.

— You are receiving this because you commented.

Reply to this email directly, view it on GitHub https://github.com/fsharp/vim-fsharp/issues/65#issuecomment-271154024, or mute the thread https://github.com/notifications/unsubscribe-auth/ABIDlOA_RimEYC1t66B4C1J2awL1Cd77ks5rQPD5gaJpZM4Ldr01 .

[mschlaipfer]

Done, but no change. :-/ This is how I tried it originally as the README doesn't mention to run install.sh. BTW, I had to add let g:syntastic_fsharp_checkers=['syntax'] to my .vimrc in order to make Synastic enable the checker.

Is there anything else that could be wrong with Syntastic or my Mono/F# installation that I can check?

[kjnilsson]

which version of mono are you using? can you enable debug and see if anything turns up in either of the two log files (instructions in readme).

On Sun, 8 Jan 2017 at 14:42 Matthias Schlaipfer notifications@github.com wrote:

Done, but no change. :-/ This is how I tried it originally as the README doesn't mention to run install.sh. BTW, I had to add let g:syntastic_fsharp_checkers=['syntax'] to my .vimrc in order to make Synastic enable the checker.

Is there anything else that could be wrong with Syntastic or my Mono/F# installation that I can check?

— You are receiving this because you commented.

Reply to this email directly, view it on GitHub https://github.com/fsharp/vim-fsharp/issues/65#issuecomment-271155208, or mute the thread https://github.com/notifications/unsubscribe-auth/ABIDlKV8wnx3quG_a56pu3AjmXQCvR56ks5rQPXXgaJpZM4Ldr01 .

[mschlaipfer]

When should those log files be created? I added the line to my .vimrc and ran similar commands as in the screen cast and can't see them in /tmp.

[kjnilsson]

They typically dump all the commands and responses sent to the completion server. when running vim can you see the mono process at all? is the server even started?

On Sun, 8 Jan 2017 at 14:58 Matthias Schlaipfer notifications@github.com wrote:

When should those log files be created? I added the line to my .vimrc and ran similar commands as in the screen cast and can't see them in /tmp.

— You are receiving this because you commented.

Reply to this email directly, view it on GitHub https://github.com/fsharp/vim-fsharp/issues/65#issuecomment-271156055, or mute the thread https://github.com/notifications/unsubscribe-auth/ABIDlP090GWHHV379h5O6OAKoCLGNSdsks5rQPmSgaJpZM4Ldr01 .

[mschlaipfer]

It seems like only the one for VSCode is started.

I forgot the mono version before: Mono JIT compiler version 4.6.2 (Debian 4.6.2.7+dfsg-1)

[kjnilsson]

Ok linking a while bunch of similar installation related issues, several of them linux related. Perhaps if you scan through them you'll find something that may be related.

https://github.com/fsharp/vim-fsharp/issues/58 https://github.com/fsharp/vim-fsharp/issues/49 https://github.com/fsharp/vim-fsharp/issues/43 https://github.com/fsharp/vim-fsharp/issues/42 https://github.com/fsharp/vim-fsharp/issues/41 https://github.com/fsharp/vim-fsharp/issues/33 https://github.com/fsharp/vim-fsharp/issues/37

[kurka]

Had a similar problem as @mschlaipfer , but in my case vim-fsharp was conflicting with fsharp-vim. I think it is a good idea to add to README that both fsharpbinding-vim and fsharp-vim might conflict with vim-fsharp.

[kjnilsson]

@mschlaipfer is this still an issue? Can you try the latest version?

[mschlaipfer]

@kjnilsson I haven't solved it back then, I will have a look again.