Chromatica can't find libclang_path

[kwon-young]

Hello,
I have some trouble to make chromatica work.
I'm using:

• ubuntu 16.04
• libclang 3.8
• python 2.7
• neovim 0.2.0

I've set

let g:chromatica#libclang_path="/usr/lib/llvm-3.8/lib/libclang.so"

But when doing ChromaticaStart, I still have the same error message:

[chromatica] There was an error starting chromatica. Please check g:chromatica#libclang_path.

Is there any way to see what is not working here ?

Also, what does g:chromatica#enable_debug does ?
i've tried to set it, but nothing changed.
Could you document it ?

[arakashic]

I apologize for the confusion on the error message. It basically is a catch-all message when chromatica failed to start. I think the problem is you are using python 2.7 while chromatica is written in python 3.

the g:chromatica#enable_debug is just enabling the debug log for chromatica. It only works after chromatica is started, so not very helpful in your case.

I will add a section in the document to talk about the diagnostic setting for it.

[kwon-young]

Using python 3.5 solve the issue.
Maybe it would be useful to indicate in the help that it doesn't work with python 2.7 ?

[arakashic]

Are you referring to junegunn/seoul256.vim? Since I haven't test the
compatibility with color schemes, there could be a compatibility issue
between Chromatica and seoul256. I can give a try and maybe hack a little
bit on my side.

On Fri, Nov 11, 2016 at 6:42 AM Kwon-Young Choi notifications@github.com
wrote:

Closed #27 #27.

—
You are receiving this because you commented.

Reply to this email directly, view it on GitHub
#27 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA0dOvLbaDVS42KZ6ysX6PRvSbVCGe0qks5q853WgaJpZM4Kuts7
.

Yanfei Guo
yanf.guo@gmail.com

[kwon-young]

That could be awesome !
I don't know a lot about vim syntax highlighting system but I'd happy to help.

And yes, i was talking about junegunn colorscheme

[arakashic]

I have try to create a minimal vimrc with seoul256. Chromatica works
normally with seoul256 (without any extra setting). Were you starting nvim
with seoul256 or switch to it from a different colorscheme after starting
nvim? I noticed that if I change the colorscheme, the color is not updated
correctly.

On Fri, Nov 11, 2016 at 4:57 PM Kwon-Young Choi notifications@github.com
wrote:

That could be awesome !
I don't know a lot about vim syntax highlighting system but I'd happy to
help.

—
You are receiving this because you commented.

Reply to this email directly, view it on GitHub
#27 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA0dOuMWdDfxlglzn82XFIZzS2aSCT9bks5q9PLpgaJpZM4Kuts7
.

Yanfei Guo
yanf.guo@gmail.com

[kwon-young]

Thanks for your reply.
Indeed the colorscheme works.
I think it's just that my python installation was a mess (i installed anaconda 3 with python 3 by default)

[sasq64]

I'm having the same issue. Ubuntu 17.10, Neovim, neovim-python2 & neovim-python3 all 0.2.0
I installed python support with a single call to "pip install neovim"

EDIT: Tried with libclang 5.0, 4.0 and 3.9

[goirijo]

I'd like to point out another possible solution for anyone encountering the same issue. I was getting the same error despite having python3 installed and the correct path to libclang. What ended up solving it form me was running UpdateRemotePlugins.