bigfish / vim-js-context-coloring

JavaScript Context Coloring in Vim
MIT License
151 stars 8 forks source link

No matching autocommands #22

Open gunar opened 8 years ago

gunar commented 8 years ago

Today my vim-js-context-coloring simply won't work anymore.

When I try to toggle it, I get No matching autocommands.

I've tried to remove it completely and install again, but no luck.

I'm using neovim with neovim branch and I have npm installed in ~/.nvim/bundle/vim-js-contenxt-coloring and /rpluing/node as well. Running :UpdateRemotePlugins spits out: (if that helps)

function <SNR>43_UpdateRemotePlugins..<SNR>43_RegistrationCommands, line 16                                                                                    
Vim(let):Channel was closed by the client                                                                                                                      
remote/host: python3 host registered plugins ['unite.py']                                                                                                      
Press ENTER or type command to continue
bigfish commented 8 years ago

I'm seeing the exact same issue. Will let you know once I find out what broke..

bigfish commented 8 years ago

huh, so what I did is I clobbered both node_modules in main part of repo, and the one in rplugin/node and then ONLY npm install inside the rplugin/node dir. Then load vim, run 'UpdateRemotePlugins' and reload vim again with a js file. I think the node_modules in root are messing up stuff, somehow? I should probably remove the root package.json in the neovim branch.

bigfish commented 8 years ago

ugh, still getting the error..

bigfish commented 8 years ago

Right. I remembered that I ran into a similar recently, https://github.com/neovim/node-host/issues/9

For some reason, you need to install debug version on neovim to get debug errors in ~/.nvimlog

So I installed debug (HEAD) version to get more error info

Looks like this may be an issue in node-host, as someone else is getting the same error https://github.com/neovim/node-host/issues/10

bigfish commented 8 years ago

This appears to be caused by latest node version breaking node-host .. what version of Node are you using ? It is working for me on Node 5.4.1, so if you downgrade to that for the moment it should work, until the node-host bug is fixed.

gunar commented 8 years ago

I see. I'm running v5.6.0.

I wanted to help out but yeah you know... time flies. Thank you very much for checking it out.

bigfish commented 8 years ago

the issue is mostly fixed downstream, until node-host is updated, you can go into the node-host plugin dir, wipeout the node_modules, then update the required version of "node-client" in its package.json, to be 1.0.8. Then do the usual UpdateRemotePlugins, and reload nvim.

bigfish commented 8 years ago

^ do npm install obviously, after updating the package.json