-
Notifications
You must be signed in to change notification settings - Fork 34
syntax checking does not work #90
Comments
I don't really test with neovim. Does it work with normal vim?
|
Just tried on a fresh installation of normal vim (debian vim v8.0) with only Synastic and vim-fsharp plugins. Same there. The syntax checking does not work properly.
|
did you install mono and run |
Yes, mono etc are installed, and the installation seems okay. For example, if I reload the .fs file using |
I will try to look into this but you could create a Vagrantfile or similar with a repro it would allow me to investigate it more quickly. |
I have the same issue on os x (vim 8.0 compiled with python3) using vim plug. Pathogen is installed and everything. The rest seems to work just fine it is just the type checking that does not work. The type checking seems to show up at random and doesn't refresh when writing. It also seems to show the same errors even when changing file. How can I create a Vagrantfile to allow you to investigate? |
It could be lagging behind too much. Does it update correctly when you
write the buffer?
…On Sun, 14 Jan 2018 at 09:21, MarcCoquand ***@***.***> wrote:
I have the same issue on os x (vim 8.0 compiled with python3) using vim
plug. Pathogen is installed and everything. The rest seems to work just
fine it is just the type checking that does not work. The type checking
seems to show up at random and doesn't refresh when writing. It also seems
to show the same errors even when changing file.
How can I create a Vagrantfile to allow you to investigate?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#90 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABIDlHVuhd-wO6MZPGaIOL6kf2RDSx-sks5tKccQgaJpZM4OGPD_>
.
|
Bump |
@mudrasone I have issues with python3 and normal vim atm. Perhaps the same applies to neovim. Are you able to run neovim with python2 as a test? |
@kjnilsson The error I experienced was with
How is Python supposed to be setup? Edit: Related junegunn/vim-plug#695 |
Looks like python support isn't installed: see https://github.com/fsharp/vim-fsharp#troubleshooting |
I installed the required pip neovim package so the Neovim reports python 2 and 2 are "had", but I'm still experiencing the same issue I with vim. The Fsi commands run properly, I'm wondering if the issue could just be with Syntastic? |
It may be, it can be very hard to tell sometimes, it works ok for me with vim with python2 support. At some point I will consider removing Syntastic in favour of Ale and at the same time remove the python requirement all together. |
Today I decided to try rewriting my Elm app w/ Bolero to see if Bolero could ease some of the troubles of having to go between Servant+Haskell & Elm. Ran into issues with the plugin. Went through the troubleshooting steps and made sure I I'm pretty turned off by the fact that there's no ALE support for fsharp so I reluctantly installed Syntastic hoping I'd be good to go from there. Then I ran into an error about
I'm reluctantly installing VSCode to see if it'll "just work" but it's a bummer not to be able to use my favorite editor to try out the language :/ |
@erlandsona try https://github.com/ionide/Ionide-vim - it works really well. |
The syntax checking does not work. A few symptoms:
b:fsharp_buffer_changed
is not updated correctly. Even the file is edited, its value is kept as 0.I am using neovim 0.2.0, and python3. Thanks.
The text was updated successfully, but these errors were encountered: