Skip to content
This repository has been archived by the owner on Apr 1, 2020. It is now read-only.

Missing parenthesis #29

Closed
gglanzani opened this issue Dec 5, 2016 · 9 comments
Closed

Missing parenthesis #29

gglanzani opened this issue Dec 5, 2016 · 9 comments

Comments

@gglanzani
Copy link

Hi all,

I'm trying to run :CheckHealth, but I do get this error:

C:\Users\x\AppData\Roaming\npm\node_modules\oni-vim\vim\vimfiles\jedi-vim\autoload\health\jedi#check
================================================================================
  - ERROR: Failed to run healthcheck for "C:\Users\x\AppData\Roaming\npm\node_modules\oni-vim\vim\vimfiles\jedi-vim\autoload\health\jedi#check" plugin. Exception:
    Vim(call):E107: Missing parentheses: C:\Users\x\AppData\Roaming\npm\node_modules\oni-vim\vim\vimfiles\jedi-vim\autoload\health\jedi#check()

I'm using Windows 10, installed oni via npm

@bryphe
Copy link
Member

bryphe commented Dec 5, 2016

Hi there,

Interesting, I just tried it too, and see a similiar issue:

D:\oni\bin\x86\Neovim\share\nvim\runtime\autoload\health\nvim#check
================================================================================
  - ERROR: Failed to run healthcheck for "D:\oni\bin\x86\Neovim\share\nvim\runtime\autoload\health\nvim#check" plugin. Exception:
    Vim(call):E107: Missing parentheses: D:\oni\bin\x86\Neovim\share\nvim\runtime\autoload\health\nvim#check()

D:\oni\bin\x86\Neovim\share\nvim\runtime\autoload\health\provider#check
================================================================================
  - ERROR: Failed to run healthcheck for "D:\oni\bin\x86\Neovim\share\nvim\runtime\autoload\health\provider#check" plugin. Exception:
    Vim(call):E107: Missing parentheses: D:\oni\bin\x86\Neovim\share\nvim\runtime\autoload\health\provider#check()

These look like the Neovim/vim runtime plugins.

Regarding jedi-vim, there could be a separate issue, though - I've packaged a Windows neovim binary, but it doesn't have python support. For the version I've bundled, it doesn't look like it has python support, as echo has('python') and echo has('python3') both return false. You might want to try modifying it to use your build. You can modify that it in NeovimInstance.ts when it spawns the process at the bottom. We should have a Config setting for this too.

@gglanzani
Copy link
Author

@extr0py Thanks!

I still have to build a neovim for Windows. I'll probably download it from the AppVeyor CI then.

I'll try to let you know (maybe tonight).

@gglanzani
Copy link
Author

@extr0py It seems that even with the latest binaries there's no Python luck.

See neovim/neovim#5360 (in particular this bit neovim/neovim#5360 (comment) ) and the PR that should fix it is still open neovim/neovim#5280

I guess I'll patiently wait ;)

@bryphe
Copy link
Member

bryphe commented Dec 7, 2016

Ya, bummer :( I was looking for a distribution too with Python so I could use Ultisnips but no luck. I'll close this for now then, since it's tracked by a Neovim issue.

The good news is I believe we could still support a python language service like Jedi, even without Python integration directly in Neovim. If you're interested in that, we can track in a separate issue. I'll close this for now though since it's not an Oni issue.

Cheers!

@bryphe bryphe closed this as completed Dec 7, 2016
@gglanzani
Copy link
Author

I would wait first for Python support for nvim on Windows. It's a target for 0.2 anyway, and work is underway.

This could save us lots of time.

@justinmk
Copy link

justinmk commented Jan 9, 2017

FWIW, CheckHealth should work in Windows using the neovim HEAD build (now linked from AppVeyor).

@bryphe
Copy link
Member

bryphe commented Jan 9, 2017

@justinmk - Nice! Thanks for the update! I'll pick up the binaries soon

@justinmk
Copy link

justinmk commented Jan 9, 2017

@extr0py If you were previously using @equalsraf's binaries (from neovim/neovim#810) I'd wait ~1 week. I'm working on merging all the remaining Windows patches to master, in an effort to get Windows support up to par. Until then, master is a "behind" neovim/neovim#810 in some respects.

@bryphe
Copy link
Member

bryphe commented Jan 9, 2017

@justinmk - cool, thanks for the heads up! I'll wait for the Windows patches to make it in.

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

No branches or pull requests

3 participants