Skip to content
This repository has been archived by the owner on Mar 12, 2024. It is now read-only.

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

Open
mschlaipfer opened this issue Jan 8, 2017 · 20 comments
Open

Comments

@mschlaipfer
Copy link

mschlaipfer commented Jan 8, 2017

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
Copy link
Contributor

kjnilsson commented Jan 8, 2017 via email

@mschlaipfer
Copy link
Author

mschlaipfer commented Jan 8, 2017

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
Copy link
Contributor

Python 2 support in vim?

@mschlaipfer
Copy link
Author

echo has('python') is 1

@kjnilsson
Copy link
Contributor

kjnilsson commented Jan 8, 2017 via email

@mschlaipfer
Copy link
Author

mschlaipfer commented Jan 8, 2017

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
Copy link
Contributor

kjnilsson commented Jan 8, 2017 via email

@mschlaipfer
Copy link
Author

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
Copy link
Contributor

kjnilsson commented Jan 8, 2017 via email

@mschlaipfer
Copy link
Author

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

@kjnilsson
Copy link
Contributor

kjnilsson commented Jan 8, 2017 via email

@mschlaipfer
Copy link
Author

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
Copy link
Contributor

kjnilsson commented Jan 8, 2017 via email

@mschlaipfer
Copy link
Author

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
Copy link
Contributor

kjnilsson commented Jan 8, 2017 via email

@mschlaipfer
Copy link
Author

mschlaipfer commented Jan 8, 2017

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
Copy link
Contributor

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.

#58
#49
#43
#42
#41
#33
#37

@kurka
Copy link

kurka commented Jan 11, 2017

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
Copy link
Contributor

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

@mschlaipfer
Copy link
Author

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

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants